Read the status of background work
Guarded by a key, but by **no scope at all** — the only route in v1 that is. A job is born from a call whose scope was already checked, so asking for its progress needs nothing further. Do not infer scopes from the pattern of other routes here.
Try it — GET /jobs/{id}
Kept for this tab only — it disappears when you close it, and it is never sent anywhere except as the Authorization header on the call below.
Authorization
bearerAuth Authorization: Bearer sk_live_.... Keys in the query string or the
request body are refused — a URL is logged by every proxy it passes,
and that is how customer keys leak.
A key carries scopes. A call outside them answers 403 with
insufficient_scope and names the scope it wanted.
In: header
Path Parameters
The prefixed id of the object.
Response Body
application/json
application/json
application/json
application/json
curl -X GET https://app.sendkuy.com/api/v1/jobs/job_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3 \ -H "Authorization: Bearer sk_live_YOUR_API_KEY"{ "data": { "object": "job", "id": "job_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3", "type": "contacts.bulk", "status": "queued", "total": 0, "processed": 0, "failed": 0, "errors": [ {} ], "created_at": "2019-08-24T14:15:22Z", "completed_at": "2019-08-24T14:15:22Z" }}