Skip to main content

API Troubleshooting

Applies toQuery APIJobs API

These are the "my calls are going through, but something's still off" issues on the Query and Jobs APIs. This page is symptom-indexed — find the thing you're seeing, get the one move that fixes it, and a pointer to the page that owns the full detail.

Three neighbors own the problems that aren't here:

Your download loop keeps returning the same results​

You page through /jobs/{job_id}/result-files and keep getting the same files back, or the loop never terminates. Each response includes a next pagination token, and resending the same request unchanged returns the same page every time.

Fix: send the next token back on each request, carrying it forward page by page. The full round-trip is in Jobs API quickstart → Download the results.

Downloads start failing with 429 partway through a large job​

A big backfill downloads fine for a while, then requests for result files start returning 429. Pulling every file back-to-back the moment a job completes is the common way to hit the fair-use ceiling.

Fix: download files as each page becomes available while the job is still running, rather than all at once at the end, and treat a 429 as a signal to slow down, not a hard failure. See Rate limits → REST APIs and Errors → Retrying REST calls.

A job shows canceled but you never canceled it​

A job you left running comes back in a canceled state with no action from you. A job that isn't checked for 2 hours is auto-canceled for inactivity — and listing jobs doesn't count as a check; the check has to be a poll on the job's own ID.

Fix: poll the job by its ID to keep it alive. If one does lapse, resume continues from where it left off — you don't lose progress. Details in Jobs API quickstart → Poll until it's done.

results_available is false — the job isn't broken​

A result-files response comes back with results_available: false and you're not sure whether to retry or restart. It just means that page isn't ready yet.

Fix: wait, then retry with the same next token you already have — it's neither an error nor a reason to resubmit the job.

result-files returns nothing (or a 405) when you POST​

Listing result files fails or comes back empty, often after copying an older example that used POST. Some older documentation showed a POST for this call.

Fix: call /jobs/{job_id}/result-files as a GET — the current spec is correct. The download round-trip is in Jobs API quickstart → Download the results.

Query API returns fewer rows than you expect​

A Query call returns about 10 results when you expected the full set. Result size defaults to a small page.

Fix: compare the total in meta.docs against the rows you got back, and page through — the pattern is in the Query API quickstart.

Getting help​

If you hit a REST issue that isn't listed here, email support@edited.com with the surface (Query or Jobs), the endpoint and request body you sent, and the full response you got back.