NewSee how
FirstSales
Home/Tutorials/Monitor API keys: logs & usage
Developer & CLI

Monitor API keys: logs & usage

Inspect Developer API request logs and usage stats — per-key and per-route request counts, error rates, and latency — to debug integrations and spot abuse.

6 min read·Intermediate·6 steps
  1. 1

    What you can monitor

    Every Developer API key's requests: per-key and per-route counts, error rate, latency, and individual request logs with request IDs.

  2. 2

    Open Settings → API

    The API section has three tabs: API Keys, Logs, and Usage. This section is admin/owner only — other roles see a notice that key management is restricted.

  3. 3

    Read the Usage tab

    Totals over a rolling window (default 7 days): total requests and overall error rate, then a breakdown by key and by route so you can see which key or endpoint drives traffic and errors.

    Read the Usage tab
  4. 4

    Drill into the Logs tab

    Each request row shows the method, route pattern, HTTP status, latency (ms), the key prefix that made it, an error code (if any), and a request ID for support.

  5. 5

    Debug a failing integration

    Scan Logs for non-2xx status values, read the errorCode, and match the keyPrefix to the key doing the damage. Quote the requestId when contacting support.

  6. 6

    Spot abuse or a runaway script

    A spike in a single key's requests in the by key breakdown, or a climbing error rate in Usage, is your signal to revoke that key in the API Keys tab and reissue a properly scoped one.

Pro tips

Hard-won shortcuts that keep warm-up on track.

1

Start in Usage, drop into Logs

Use Usage to see the shape of the problem — which key, which route, how bad — then jump to Logs for the individual failing requests. Top-down is faster than scrolling raw logs.

2

The request ID is what support needs

Copy the request ID from a failing log row instead of describing "a 500 earlier today" — it's the fastest way to get help.

3

Check scopes before blaming the API

A rising error rate on one key usually means an expired assumption in that integration (renamed field, revoked scope) — check that key's scopes first.

4

Role-check before debugging access

Only admins/owners see this section; if a teammate "can't find API logs," check their role before assuming something's broken.

Frequently asked questions

Does FirstSales expose API request logs?

Yes — Settings → API → Logs shows per-request method, route, status, latency, key prefix, error code, and a request ID.

Where do I see how much my keys are used?

The Usage tab: total requests, error rate, and breakdowns by key and by route over a rolling window (7 days by default).

Who can view API logs and usage?

Only organization admins and owners. Other roles see a notice that key management is admin/owner-only.

How do I debug a failing API call?

In Logs, find the request by non-2xx status, read its errorCode, note the keyPrefix and requestId, and share that ID with support.

A key looks compromised — what do I do?

Revoke it in the API Keys tab and issue a new one with only the scopes it needs; watch Usage's per-key counts to confirm the traffic stops.

Can I change the usage window?

The Usage view defaults to the last 7 days. Use the Logs tab (with its filters) for narrower, request-level inspection.

Ready to put this into practice?

Start your FirstSales trial and launch a warmed, authenticated mailbox in minutes.

Start for $1
All tutorials