API & MCP documentation

Base URL: https://tickets.cruceconsulting.com · Developer docs are English-only; the product UI is available in ES/EN/FR/DE.

Authentication

Create an API key at /api-keys (any signed-in user). The key inherits your exact role and scope — a client-company key only sees that company's tickets — and every action is recorded in the audit trail under your name. Send it as a bearer token:

curl https://tickets.cruceconsulting.com/api/tickets \
  -H "Authorization: Bearer folio_YOUR_TOKEN"

Tokens are shown once at creation and stored hashed. Revoke them anytime from the same page.

Limits & pricing

Rate limit: 30 requests/minute per key during the free trial; 60 requests/minute on paid subscriptions (HTTP 429 beyond it). Included API keys per plan: Base 1 (additional keys USD $150/month), Growth 3, Enterprise unlimited. Plans also cap client companies, internal teams and users — see the Terms. To upgrade, contact support@cruceconsulting.com.

REST endpoints

All endpoints exchange JSON. Errors return { "error": "...", "code": "stable_code" }.

Method & path	Description
GET /api/auth/me	Who am I (role, tenant, company)
GET /api/tickets	List tickets. Query: state (open|closed|all), status, tramite, company, aging=8, correo=0
POST /api/tickets	Create. Required: external_ref, fecha_solicitud (YYYY-MM-DD), tramite_type_id (+ fields your org hasn't hidden). Provider keys add client_company_id
GET /api/tickets/:id	Detail: fields, checklist steps, comments, full audit history
PATCH /api/tickets/:id	Update fields (client keys: client fields; provider keys also status_id, correo_recibido, cerrado, fecha_entrega). Audited
POST /api/tickets/:id/comments	{ body, internal? } — internal is provider-side only
PATCH /api/tickets/:id/steps/:stepId	{ done: bool } — checklist toggle (provider-side)
GET /api/dashboard	Metrics for the key's scope
GET /api/tenants/:id/statuses · /tramite-types · /field-settings	Configuration reads (ids needed for creating/updating)
GET /api/tenants/:id/export	Full JSON export (admin keys)

MCP (Model Context Protocol)

Folio exposes an MCP server so AI assistants can work with tickets under your permissions. Endpoint: https://tickets.cruceconsulting.com/mcp (Streamable HTTP, bearer auth).

Claude Code:

claude mcp add --transport http folio https://tickets.cruceconsulting.com/mcp \
  --header "Authorization: Bearer folio_YOUR_TOKEN"

Claude Desktop / other MCP clients (config JSON):

{
  "mcpServers": {
    "folio": {
      "type": "http",
      "url": "https://tickets.cruceconsulting.com/mcp",
      "headers": { "Authorization": "Bearer folio_YOUR_TOKEN" }
    }
  }
}

Tools: list_tickets, get_ticket, create_ticket, update_ticket, add_comment, get_dashboard, get_config. Start with get_config to obtain status/category/company ids. User management, imports and configuration changes are deliberately not exposed.

Support: support@cruceconsulting.com · Terms · Privacy