API Reference
Job Status
Query status and output information for a job.
Endpoint
GET /v1/jobs/{job_id}
Example Request
curl -X GET https://api.removebgvideo.com/v1/jobs/{job_id} \
-H "X-Api-Key: YOUR_API_KEY"Status Values
| Status | Meaning |
|---|---|
| pending | Accepted, waiting for processing |
| processing | RunPod worker is processing |
| completed | Output available |
| failed | Job failed, check error |
Response Fields
| Field | Type | Description |
|---|---|---|
| id | string | Job id |
| status | string | Job status |
| progress | number | 0-100 progress |
| output_url | string|null | Processed asset URL when completed |
| error | string|null | Error message when failed |
| created_at | string | UTC time |
| duration_seconds | number|null | Output duration |
| billing_status | string|null | Credit charge status |
API Contract Notes
- All clients should handle non-2xx responses as structured error payloads.
- Use explicit JSON schema validation for request payloads on your side.
- Treat output_url as an asynchronous artifact and not an immediate response contract.
- Persist job lifecycle state transitions for auditing and support.
Integration Verification
| Check | How to Verify |
|---|---|
| Authentication | Call endpoint with valid and invalid key, confirm 200 vs 401 |
| Rate limits | Burst test and confirm 429 handling with backoff |
| Idempotency | Retry same request and verify no duplicate side effects |
| Observability | Confirm request_id/job_id appears in logs and dashboards |
Status Polling Policy
- Start with 2s interval, back off to 5-10s for long jobs.
- Stop polling on completed/failed terminal states.
- Persist last known status to survive worker restarts.
When to Use Job Status
Job Status belongs to the API Reference section and covers query status and output information for a job.
The page is written for developers and operators who need predictable video background removal behavior in production, not just a one-off demo request.
- Validate the exact Job Status contract before wiring it into backend workers or customer-facing flows.
- Use the field tables and examples to create request/response tests in staging.
- Capture job_id, request_id, model, output_format, and user context whenever this endpoint participates in a production workflow.
Implementation Notes
Before you promote this workflow, test it with at least one short clip, one longer clip, and one visually difficult clip from your actual product or customer segment.
For support and debugging, persist the original input reference, selected model, output format, credit usage, and final job status alongside your internal user or project id.
- Do not assume a processing request returns a finished video immediately; completed output is asynchronous.
- Do not discard failed-job payloads before logging the error code and request context.
- Do not let polling loops run without timeout, backoff, or terminal-state handling.
FAQ
| Question | Answer |
|---|---|
| Is Job Status required for every integration? | Use it when your integration calls this endpoint directly; otherwise review it to understand the contract behind SDK helpers. |
| What should I test before going live? | Verify success, failure, timeout, retry, and insufficient-credit paths with realistic video files and the same output format you plan to ship. |
| How does this connect to the rest of the API? | Most workflows connect upload or source URL handling, job creation, status polling, output retrieval, usage tracking, and operational logging. |