Skip to main content
Stophy keeps a record of each call you paid for: which endpoint, when, with which key and what it cost. It never keeps what you sent or what came back. These calls are free and need an API key. For your balance and spending over time, see Usage.

List your recent calls

GET /v1/logs lists your billed calls, newest first, 50 to a page.
This real response is cut to two calls. The key id and name are examples.
The answer also has an endpoints list with every endpoint id you can filter by. Only calls that were billed are logged. A free call, an error and an empty result have no entry. A call with zero data retention is logged with its endpoint and cost, and nothing else. Logs are kept for 90 days.

Read one call

GET /v1/logs/{id} takes the requestId of any answer. It looks back days days, 7 by default and up to 90.
charges is how many times the call was charged. A crawl or a batch is charged once for each page, so one request id can have many charges. A request id that was not billed in that time answers 404 with code notFound.

List your billed calls by cursor

GET /v1/team/activity returns the same calls in a shorter shape, with a cursor instead of page numbers. It is free.

See your running jobs

GET /v1/team/queue-status counts your crawl, batch and agent jobs that are running or waiting.
maxConcurrency is how many jobs can run at once on your tier. mostRecentSuccess is when your last billed call finished. See Rate limits.

See what extract and agent used

Extract and agent use a model. GET /v1/team/token-usage shows this month’s use, in tokens: 15 tokens for each $0.002 that extract and agent cost.
This is the real shape with example numbers. remainingTokens is your balance counted in tokens, and the plan and period fields are null because there are no plans. GET /v1/team/token-usage/historical returns one row for each month with tokensUsed, and byApiKey=true splits each month by key.

Match a request to its log

Save the requestId of every call you care about. It is in the body of each answer and in the X-Request-ID header, and it is the id GET /v1/logs/{id} and feedback take. See Troubleshooting.