Developer console

The in-app console for watching Embed API traffic, tracking usage, and managing API keys.

What is the Developer console and when would I use it?

The Developer console is where you monitor and manage your Embed integration from inside Coassemble. Open it when you are wiring Coassemble into your own product, checking that the API is healthy, tracing a specific request or client, or keeping an eye on usage against your allowance.

It sits alongside the full developer documentation at developers.coassemble.com, which covers the API reference, embeddables, events, webhooks, and errors and rate limits. The console is the operational view. The developer docs are the reference.

The console has six tabs: Overview, Requests, Webhooks, Clients, Usage, and API keys.

Who can see the Developer console?

Only people in your workspace with the Developers or Owners role see the Developer console. Creators do not see it.

Legacy accounts that do not have API access do not have the Developer console at all. If you are on an older plan and cannot see the Developer option in Coassemble, that is why.

Overview

The Overview tab is a health dashboard for your Embed traffic. It shows:

• Requests in the last 24 hours, with the previous 24 hours next to it for comparison.
• Errors in the last 30 days, excluding 404s, so noise from missing paths does not drown out real problems.
• p95 latency, the response time that 95% of requests came in under.
• Webhooks delivered, so you can see delivery is flowing.
• A requests and errors chart across the recent window.
• Recent failures grouped by endpoint, so a spike shows up as a single row rather than a wall of individual errors.

The tab also surfaces a short attention list at the top when it spots something worth looking at, such as a jump in errors or a webhook endpoint that has stopped delivering. When traffic is quiet and nothing needs a look, that space stays clear instead of showing empty charts.

When you'd use it: as your first check when something feels off, or as a quick daily glance to confirm the integration is behaving.

Requests

The Requests tab is a searchable log of every call made against your API keys. Each row shows the time, the request (method and path), the status code, the duration, the client identifier, and the request ID.

Filters:

• Time range
• Status (for example, only 4xx or only 5xx)
• Path contains (free-text match on the path)
• Client identifier (narrow to one integration or one customer)
• Hide 404s toggle

Open any row to see the request detail, including why a call was refused when that is the reason for the status. A response that would otherwise read as a bare error code is explained in plain words, for example that a feature is not enabled for the workspace, so refusals do not look like faults in your integration.

You can export the filtered log as a CSV. Requests are retained for 30 days.

The request ID is the same ID Coassemble returns in the API response, so you can copy it out of your own logs and paste it straight into the filter.

When you'd use it: tracing a specific failure a customer reported, checking what a particular client identifier is doing, or pulling a slice of traffic out as CSV for a deeper look.

Webhooks

The Webhooks tab is where you manage the endpoints Coassemble posts events to, and watch what happens to each delivery. It has three parts.

Your endpoints. The list of subscriptions for your workspace: the endpoint URL, the events it is subscribed to, and its signing secret. The signing secret is shown so you can verify that a delivery genuinely came from Coassemble. Every request Coassemble posts is signed, and the developer docs at developers.coassemble.com cover the delivery headers and the exact signature check.

Delivery history. Each attempt against each endpoint, with the status code we got back and the response body. When a delivery fails, you can replay it, either one at a time from its row or in bulk for a whole batch of failures, which is what you reach for when your endpoint has been down for a stretch and you want the missed events to catch up.

Events we send. A reference list of the events Coassemble emits, kept as a collapsed section at the bottom of the tab so it does not take permanent room on the working screen. Expand it when you want to check which events are available before you subscribe to them.

The full event catalogue and payload shapes live in the developer docs under Events and Webhooks at developers.coassemble.com.

When you'd use it: setting up a new subscription, checking your endpoint is receiving deliveries, replaying deliveries after an outage on your side, or picking up the signing secret to verify signatures.

Clients

The Clients tab is a search-and-summary view over your client identifiers. A client identifier is how you tell Coassemble which of your customers a request is for, so this tab is the way to see any one of them at a glance.

The table shows, per client identifier:

• Requests in the last 30 days
• Failures in the same window
• Standing (a health indicator for that client)

The "Find a client identifier" search jumps you straight to one client.

For the concept behind client identifiers and how they attach to requests, see "How identities work" in the developer docs at developers.coassemble.com.

When you'd use it: answering a support question from one of your customers, spotting a client that is generating an unusual number of failures, or confirming a new client identifier is being picked up.

Usage

The Usage tab shows what your workspace is consuming against its allowance. It has two parts.

AI allowance, resetting monthly:

• Narration tokens
• Image generation

Creator seats, with headline counters for:

• Active clients
• Active creators
• Course views

Underneath, two tables:

• Per-creator table: identifier, client identifier, date added, date removed.
• Per-client usage table: creators, narration, images, standing.

When you'd use it: checking how close you are to your monthly AI budget, working out which client is driving the most usage, or reconciling seat activity across your customer base.

The specific numeric allowances that appear here depend on your plan. This article does not list plan-by-plan limits. Check your workspace's Usage tab for the current figures.

API keys

The API keys tab is where you create, name, and manage the keys you use to authenticate to the Coassemble API.

The table lists each key with:

• Name
• Key (masked, with the last few characters shown so you can tell them apart)
• Created date
• Last used date
• Status (active or revoked)

For how requests are counted and throttled, see "How rate limits work" in the developer docs at developers.coassemble.com.

How do I create an API key?

1. In Coassemble, open Developer, then API keys.
2. Click Create key.
3. Give the key a name that says where it will be used. Something like "Production backend" or "Staging import job" beats "Test key 3".
4. Copy the key straight away and store it in your integration's secret store. The API keys table only ever shows the masked version of a key (the last few characters), so save the full key when you create it or you will need to create a new one.
5. Keep the key out of source control.

Revoke a key from the same tab as soon as it is no longer in use, or if you suspect it has leaked. A revoked key stops working immediately.

What's the best way to rotate an API key?

The safest way to rotate a key is to overlap the new one with the old, confirm nothing is still using the old key, and then revoke it. Rotating with a gap risks failed requests. Revoking before you've checked risks the same.

1. In the Developer console, open the API keys tab and create a new key. Copy it straight away and store it in your secret store.
2. Update your integration to use the new key. If you have more than one service, job, or environment calling Coassemble, update all of them.
3. Watch the Requests tab and confirm the old key is no longer in use. Filter by the clients or endpoints you expect to have moved across, and give it long enough to cover anything that runs on a schedule (nightly jobs, weekly rollups, scheduled imports).
4. Once you are confident nothing is calling with the old key, revoke it from the API keys tab.

A revoked key stops working immediately, so anything you missed will start failing straight away. If that happens, create a fresh key, update the missed integration, and rotate again from step 3.

Rotate keys on a schedule that fits your security policy, and any time you suspect a key has leaked.

Where the full developer documentation lives

The full API reference, embeddables, events, webhooks, identities, and errors and rate limits guides live at developers.coassemble.com. The Developer console is the in-app companion to those docs.

Frequently asked questions

Does the console show usage in real time?

The Overview counters use a rolling 24-hour and 30-day window, and the Requests log shows individual calls as they land. The Usage tab tracks against a monthly allowance for AI and against current activity for creator seats.

Can I export data from the console?

Yes. The Requests tab has a CSV export of the filtered log.

How long is request history kept?

The Requests log holds the last 30 days of calls. Older requests fall off as new ones come in.