Skip to content
ajar.Book a demo

Understanding usage

View recorded requests for your workspace.

Requests and outcomes

The Usage page shows requests made with dashboard API keys. Filter by service, browse pages of requests, and review the last 14 days of request volume in UTC. Select an operation to view its connector, request ID, API key name and masked prefix, HTTP status, time, and measured latency. Older requests may not have latency. You can open a prefilled support report from the request details. Request and response bodies are not retained. Legacy connector tokens are not attributed to a dashboard key.

Trace sub-users and request origins

Send the optional x-ajar-extra-data header with a JSON object, for example {"client_origin":"1.0.2.8","user_id":"customer-123"}. It works across connector operations and authentication helpers. The header and its serialized object are each limited to 1024 UTF-8 bytes. user_id and client_origin must be nonempty strings of at most 256 UTF-8 bytes without control characters; other JSON fields are retained too. Invalid, duplicate or oversized headers return HTTP 400 before execution. Metadata is stored with the dashboard request and shown in request details. Filter Usage by exact User ID and Client origin; both filters can be combined with service. These values are supplied by your application and never establish identity or change permissions. Do not include credentials or sensitive payloads. Older requests show metadata as not supplied.

Quota and billing

Each admitted request uses one unit of its API key's quota, including requests that later fail. Provider calls made inside that request and delivery retries do not use extra units. Recorded permission, subscription, and quota denials do not consume a unit, so Usage totals can exceed quota used. Limits reset in UTC by minute, day, or calendar month; total limits do not reset. Request counts do not add a separate monetary charge to your subscription.

Pending requests

Pending means a final outcome has not been recorded yet. Completed outcomes are retried automatically after a reporting outage. An interrupted request may remain pending because its final outcome is unknown. Do not repeat a purchase or other write solely because its Usage record is pending.

Refreshing activity

Sign in and open Usage to see recorded requests for the selected workspace. Refresh to load newer records.