Use the developer Workbench
The Workbench is the console for anyone integrating Cord with another system. It lives inside the app, so you can check your integration without leaving where you work.
Opening it
- Turn on Developer mode in Your account › Preferences. It is a preference of your account, not of the organization.
- The Developers pill appears in the bottom-right corner. Click it or press
W.
You need the Settings permission in the organization. Without it, the Workbench does not appear.
What each tab does
- Overview: requests, error rate, latency, webhook deliveries, this month’s API usage and active alerts.
- Logs: every request to the API and the MCP server. Search by path, by request id (
req_…) or by error code, and open one to see its detail, copy it as cURL or replay it in the Shell. - Errors: errors grouped by code and path, with how often each happened and how to fix it.
- Events: what happened in your account (a paid quote, a new client) and what Cord delivered to each endpoint, with the option to resend.
- Webhooks: your endpoints, their success rate and the delivery history with what Cord sent and what your server answered.
- Shell: try any API operation with your session, without creating a key. In Test it can create and change data in your test environment; in Live it only reads. It gives you ready-to-use code in cURL, Node, JavaScript or Python.
- API keys: create, roll and revoke API keys, and see authorized connections: Zapier, Make, the Gmail add-on and any app connected through OAuth.
- Health: the list of what could break your integration, like an endpoint that keeps failing or a key about to expire.
In the top bar, the Inspector (/ key) looks up any req_…, evt_… or the ID of a quote, invoice, client, product, key or webhook.
What Cord keeps and for how long
For each API request, Cord keeps its technical data: method, path, status, latency, IP, the key that made it, the request id, the error code and message, the version, the source and the Idempotency-Key. It never stores the body of the request or the response, so your clients’ data is not kept.
Logs are kept for 30 days. If you need a longer history, store in your system the request id each response returns in the Cord-Request-Id header.
FAQ
Do the Workbench or the Shell use my API quota? No. Only requests made with live keys count.
I don’t see a request I made with a test key. The Workbench shows the environment the app is in. Switch to the test environment to see what your sk_test_ keys did.
Why can’t I see a webhook’s delivery history? History, retries and resends are part of the Pro plan or higher.
The full guide is in the Workbench documentation.