RequestBeam Docs
Get Async Job
Get the status and result of an asynchronous job created by the current account.
https://api.requestbeam.com/v1/jobs/{id}Applicable Endpoints
- Seedance 2.0 and
Seedance 2.5 use POST https://api.requestbeam.com/v1/video/seedance, which returns data.jobId and requires GET https://api.requestbeam.com/v1/jobs/{id} to retrieve job status and results.
- The current GPT-Image-2 Image Generation
endpoint returns results directly through JSON or SSE and does not use Jobs.
Use this endpoint only when a creation response explicitly contains data.jobId. The request must use an API Key belonging to the same account that created the job.
GET https://api.requestbeam.com/v1/jobs/{id}Authentication
Authorization: Bearer YOUR_API_KEYPath Parameter
idstringrequiredNumeric job ID returned as jobId when the job was created.
Request Example
curl --request GET \
--url https://api.requestbeam.com/v1/jobs/123456789012345678 \
--header 'Authorization: Bearer YOUR_API_KEY'Response
idstringJob ID.
statusstringPENDING, CONNECT, PROCESSING, COMPLETED, FAILED, or CANCELLED.
inputParamsobjectInput parameters submitted when the job was created.
outputResultunknownFinal output. Image and video models return different structures.
createdAtstringISO 8601 creation timestamp.
startedAtstring | nullISO 8601 processing start time.
completedAtstring | nullISO 8601 completion time.
Success Example
{
"success": true,
"data": {
"id": "123456789012345678",
"status": "COMPLETED",
"inputParams": {
"model": "seedance-2.5",
"prompt": "Create an eight-second brand film"
},
"outputResult": [
{
"url": [
"https://video.example.com/generated/result.mp4"
]
}
],
"createdAt": "2026-08-20T08:24:00.000Z",
"startedAt": "2026-08-20T08:24:02.000Z",
"completedAt": "2026-08-20T08:26:30.000Z"
},
"requestId": "req_..."
}Polling Guidance
- Poll every 5 to 10 seconds.
PENDING,CONNECT, andPROCESSINGare non-terminal.- Read
outputResultafterCOMPLETED. - Stop polling after
FAILEDorCANCELLED. - Result URLs may expire; save completed assets promptly.
Error Responses
See Error Codes and Troubleshooting for the full code reference, protocol differences, and diagnostic steps.
Job not found:
{
"success": false,
"error": {
"code": 30000,
"message": "Job 123456789012345678 not found"
},
"requestId": "req_..."
}Accessing another account's job:
{
"success": false,
"error": {
"code": 20001,
"message": "Access denied"
},
"requestId": "req_..."
}