Skip to main content
Product jobs share one submission API and one job lifecycle. Choose a product below for its model selection, inputs, and examples. GET /v1/products lists the products enabled for your organization.

Available products

VFX and finishing

Generate

Discover your models

Set BEEBLE_API_KEY and, for internal teams, BEEBLE_TEAM_ID. Python requires requests; JavaScript examples run in Node.js.

List products

GET /v1/products returns the products enabled for your organization.
Response (200, abbreviated):
Request parameters and response schema

List models and input schemas

Replace switchx with a product ID from the table above.
Response (200): models contains each model’s id, name, input_schema, and any requires_consent value. Use the selected model’s input_schema for required inputs, types, defaults, and supported values. Request parameters and response schema Use id in requests and name for display. Complete any required model consent in Beeble Cloud before submitting.

API schemas

Each reference below renders request parameters, request bodies, and responses from OpenAPI. Model-specific inputs come from the model catalog’s input_schema. outputs is an open object in the job response schema. Its fields vary by product and model; OpenAPI does not yet define those individual fields.

Finish a SwitchX 2.0 result

SwitchX 2.0 Finish reuses a completed Standard product generation through the separate switchx_finish product. Use model_id: "switchx-2.0" with inputs.parent_job_id and inputs.target_resolution; no upload is needed. The guide covers eligible parents, transition estimates, and retrieving the new child job through the shared product-job API.

Job lifecycle

Product submissions return 202 and a public dap_… ID. Read that job for fresh status and output URLs. Reuse the same idempotency key and request body when a submission’s outcome is uncertain. See Jobs & retries.

Completion callbacks

Set a public HTTPS callback_url to receive terminal job results. Product callbacks use type: "product.job.completed" and may be delivered more than once. See Webhooks for the payload and retries.

Credit usage and availability

Charges use your organization’s Beeble Cloud credit balance. A failed job alone does not confirm a refund. Read Billing & credits for actual charge and refund fields and API keys & organizations for access requirements. Canvas and Showrunner document/conversation APIs are separate.