Operaciones de facturas
Access
Access
Login and tenant context
User
Tenant
Summary
Tenant statistics
Track throughput, review load, processor mix, and confidence routing for the current tenant.
Recent activity
Last 14 days
System health
Health and intake
- API health
- loading
- Dependencies
- loading
- Live updates
- signed out
- API base
- loading
Operations
Internal ops dashboard
Watch host pressure, queue backlog, worker freshness, dead letters, and document processing time from one place.
Queues
Workers
Failures and recovery
Document lifecycle bottlenecks
Client upload errors
Profile
My profile
Manage your login email and view tenant details.
Tenant
Tenant data
Manage tenant legal and contact details.
Usuarios
Usuarios del Estudio de Contabilidad
Invita companeros por correo y asigna roles segun tu plan.
Defaults
Tenant defaults
Configure tenant-wide upload defaults for links and processing behavior.
When disabled, uploads stay ingested after preprocessing until someone starts processing manually.
Processing settings
External processing
Control app-wide external parsing and approval thresholds. These settings apply to every tenant.
Set the external threshold to 0% to disable external calls.
El procesamiento externo de IA puede seguir activo para extraccion si esta configurado.
Notifications
Inbox
Review workflow events, approvals, failures, and other operator signals in one place.
Elige el cliente antes de cargar facturas.
Trace
Pipeline trace
Guide
How to use this page
Use this page to connect Comprobante with other systems. Create an API key for authenticated API calls, register webhook endpoints for push events, and use dead letters to recover failed deliveries.
Step 1
Create an API key
Name the key after the system that will call Comprobante. Copy it once and store it in your backend, secret manager, or automation platform.
curl \
-H "Authorization: Bearer comp_live_xxx" \
http://localhost:8787/v1/documents?limit=20&offset=0
Step 2
Add a webhook endpoint
Point the endpoint to your backend. If you set a signing secret, verify the x-comprobante-signature header against the raw JSON body before processing the event.
{
"event": "document.processed",
"eventId": "evt_123",
"tenantId": "tenant_123",
"timestamp": "2026-03-06T18:42:59.642Z",
"data": {
"documentId": "doc_123",
"status": "approved",
"confidence": 0.98,
"reviewTaskId": null
}
}
Step 3
Recover failed deliveries
If your endpoint times out or returns a non-2xx response, Comprobante retries it. After repeated failures, the event lands in dead letters. Fix the receiver, then requeue the event from this page.
curl \
-X POST \
-H "Authorization: Bearer comp_live_xxx" \
http://localhost:8787/v1/webhooks/dead-letters/00000000-0000-0000-0000-000000000000/requeue
Current webhook event types include document.processed, document.review_approved, and document.review_rejected. Use API docs and OpenAPI JSON for the full contract.
Access
API keys
New API key:
Delivery
Webhook endpoints
Recovery