Errors & troubleshooting
Resolve key, inventory and download-link errors.
On this page
Find the cause
| Symptom | What to do |
|---|---|
| 400 · Invalid request | Check product ids, complete past UTC dates and field-level details. |
| 401 · Authentication failed | Check TICKFOLD_API_KEY and whether the key was revoked. |
| 403 · Access denied | Check account ownership. For R2, check link expiry and signature. |
| 404 · Not found | Verify task, file and catalog ids. |
| 409 · Request conflict | Use the original body with an existing Idempotency-Key. |
| 403 · AUTHORIZATION_REQUIRED | No active authorization covers this file. Get a task quote and explicitly purchase authorization; previously purchased dates use the repeat rate. Expired R2 links can be refreshed free while authorization is active. |
| 429 · Too many requests | Back off; respect Retry-After when present. |
| 5xx · Service unavailable | Retry with a delay and keep the existing task id. |
| Incomplete or unpublished UTC date | Preview another range, wait for publication, or explicitly allow partial results. |
R2 links & file verification
If the signed URL has expired, request a fresh URL for the same task and file while its authorization remains active. Refreshing a link does not extend authorization. After authorization expires, explicitly purchase a new authorization. Preserve the URL query string and use a separate request without Tickfold authentication; a changed signature can also cause an R2 403.
Do not use files with a size or SHA-256 mismatch. Download to a temporary filename and verify before replacing the final file.
Still need help?
Send the requestId, task id, file id and UTC interval to support. Never include an API key or an active signed URL.
Need a hand with your data?Contact support