Your whole integration, in a panel inside the app.

Cord's Workbench is a developer panel that opens inside the app, over whatever screen you're on. It brings together API keys, webhooks, a log of every request, business events and your integration's health, with a test mode kept apart from your real data.

Start for freeView plans

Included on every plan. Any member with access to Settings can open it.

OverviewLogsErrorsEventsWebhooksShellAPI keysHealth

Your integrationLive

24 hours7 days30 days
API requests535
Error rate1.9%Failed: 10
p95 latency412msp50: 88 ms
Event deliveries95.8%183 of 191 delivered
Requests over timeSucceededFailed
17:0016:00
Top errorsView errors →
invalid_tax_id4
invalid_request2
not_found2
rate_limited1
invalid_state1
Where they come from
Node SDK291
Cord Elements96
Connected app64
MCP38
HTTP22
Workbench18
cURL6
Recent activityView logs →
200POST/v1/cotizacionesNode SDKOct 9, 16:43:28
200GET/v1/productosCord ElementsOct 9, 16:41:05
200POST/mcp/tools/call:listar_facturasMCPOct 9, 16:37:12
200PATCH/v1/clientes/9b41c2e0-3d7a-4f12-8c55-6e0b1a2d4f90Node SDKOct 9, 16:29:51
422POST/v1/clientesinvalid_tax_idNode SDKOct 9, 16:26:40
200GET/v1/meWorkbenchOct 9, 16:15:17

LOGS

Every request, with its response.

Search by route, by request id (req_…) or by error code and open any request: status, latency, the key that made it, where it came from (SDK, CLI, cURL or MCP), the API version and, if it failed, the code and message with the guide to fix it. When something fails you know within seconds whether it was a 404 because the resource does not exist or a 422 from a malformed field.

  • Filters by method, response class, key, source and period, with live mode
  • Copy as cURL or replay the request in the Workbench Shell
  • Cord does not store your request bodies: only metadata
OverviewLogsErrorsEventsWebhooksShellAPI keysHealth
Path, req_ or error codeAllGETPOSTPATCHDELETEAll2xx4xx5xxAll keysAll sources24 hoursLive
200POST/v1/cotizacionesNode SDKOct 9, 16:43:28
200GET/v1/productosCord ElementsOct 9, 16:41:05
200POST/mcp/tools/call:listar_facturasMCPOct 9, 16:37:12
200PATCH/v1/clientes/9b41c2e0-3d7a-4f12-8c55-6e0b1a2d4f90Node SDKOct 9, 16:29:51
422POST/v1/clientesinvalid_tax_idNode SDKOct 9, 16:26:40
200GET/v1/meWorkbenchOct 9, 16:15:17
200POST/v1/facturasNode SDKOct 9, 16:02:02
404GET/v1/cotizaciones/7e3b0c91-4d2a-4f6e-b8a5-2c9d1f0e6a47not_foundConnected appOct 9, 15:48:44
200DELETE/v1/cotizaciones/2d8f6a13-5b9c-4e07-a4d1-8c3f0e7b9a52cURLOct 9, 15:31:09
429GET/v1/cotizacionesrate_limitedHTTPOct 9, 15:12:33
Load more

WEBHOOKS

Endpoints you can test without waiting for a real event.

Register a URL, pick the events and save the secret. Test sends a sample delivery right away, Rotate secret changes the signature without interrupting traffic, and each endpoint's history shows its deliveries with the code your server returned.

  • X-Cord-Signature-V1 signature with a timestamp
  • Secret rotation with a grace period
  • Pause an endpoint with a switch, without deleting it
OverviewLogsErrorsEventsWebhooksShellAPI keysHealth

Webhook endpoints

Cord notifies the address you register when something happens, like an approved quote or a payment. Every notification is signed with X-Cord-Signature-V1; verify it with the endpoint's secret.

Professional plan: 3/16+ Add endpoint
https://api.crm-interno.io/cord/eventswhsec_c41e••••••••••••••Rotate secret· 4 events· last Oct 9, 16:52:09 (503)81.7%p95 1,880 mspingTestEditDelete
https://hooks.zapier.com/hooks/catch/18342071/3kz9qm/whsec_9a0d••••••••••••••Rotate secret· 2 eventsCreated by an integration· last Oct 9, 16:31:41 (200)100%p95 310 mspingTestEditDelete
https://erp.mdvalle-usa.com/webhooks/cordwhsec_3f9a••••••••••••••Rotate secretRotating — the previous secret stops working Oct 10, 16:40· 6 events· last Oct 9, 16:52:08 (200)99.6%p95 182 mspingTestEditDelete
invoice.paid200142 ms · Oct 9, 16:52:08
quote.approved200118 ms · Oct 9, 16:31:41
client.updated20096 ms · Oct 9, 16:29:52
invoice.finalized · attempt 2200204 ms · Oct 9, 15:58:40
invoice.finalized5031206 ms · Oct 9, 15:57:40
pingtest20088 ms · Oct 9, 15:40:12
https://staging.mdvalle-usa.com/webhooks/cordwhsec_71b2••••••••••••••Rotate secret· all eventsNo deliveries in 7 dayspingTestEditDelete

HEALTH

Find out before your customer does.

The Health tab gathers in one list what can break an integration: endpoints with consecutive failures or disabled, queued or exhausted events, a high error rate, 5xx errors and keys about to expire. If an endpoint keeps failing, you see it here and get a notice before Cord disables it.

  • Consecutive failures per endpoint
  • Event queue: pending, overdue and exhausted
  • Keys that expire in the next 7 days
OverviewLogsErrorsEventsWebhooksShellAPI keysHealth
Active alerts: 3Some deliveries or endpoints are failing.
https://api.crm-interno.io/cord/events: 3 failures in a rowHTTP 503Review endpoints →
Events that ran out of retries: 1Cord stopped trying to deliver them. You can resend them from Events.View events →
Key ERP · Nightly sync expires on Oct 14, 2026Move your integration to a valid key before it expires.View keys →
Endpoints
https://api.crm-interno.io/cord/eventsFailures in a row: 3
https://hooks.zapier.com/hooks/catch/18342071/3kz9qm/100% · p95 310 ms
https://erp.mdvalle-usa.com/webhooks/cord99.6% · p95 182 ms
https://staging.mdvalle-usa.com/webhooks/cordPaused
Event queue
Queued events2
Overdue retries0
Exhausted events1
p95 delivery640 ms

Cord retries each failed delivery up to 11 times with increasing backoff.

API in the last 24 hours
API requests535
Error rate1.9%
4xx10
5xx0
p95 latency412 ms

FREQUENTLY ASKED QUESTIONS

What developers ask about Workbench.

It's Cord's developer panel. It opens inside the app and brings together API keys, webhooks, the request log, grouped errors, business events, integration health, a Shell to try the API with your session and an ID inspector, with a separate test mode.

Method, route, response code, latency, IP, the key, the environment, the request id, the error code and message, the API version, the source (SDK, CLI, cURL, MCP) and the Idempotency-Key. It does not store request or response bodies, so your clients' data is never stored outside where it belongs.

Cord retries each delivery up to 11 times with growing waits, over almost four days. If the endpoint keeps failing you see it in Health and get a notice; after 5 consecutive failures Cord disables it instead of hammering a server that is down.

Any member of the organization with access to Settings. It is included on every plan.

Explore the rest of the developer platform.

MCP serverCord's MCP server connects AI assistants like Claude or Cursor to your real business data through the Model Context Protocol.
Webhooks and integrationsCord's webhooks notify your server every time something happens in your sales cycle: a quote sent, viewed, approved or paid, an invoice issued, a new client.
Cord ElementsCord Elements brings your quotes and invoices into your clients' portal with one line of code.
DocumentationGuides, API reference and examples for every endpoint.

Integrate with your eyes open.

Create your account, open the Workbench and follow your first request live.

Start for freeContact Sales

See what you'll pay

Published pricing, with the fee for every payment in plain view.

Pricing details →

Start building

Start operating and sending quotes on the Free plan.

Integration options →