Skip to main content
The APOB GraphQL API uses a single HTTP endpoint, POST /graphql. Choose a query to read existing resources or a mutation to create or change them. This reference covers account access, model and element discovery, image and video generation, speech, avatars, and generation results. Use the GraphQL URL supplied for your APOB integration as APOB_GRAPHQL_URL. The examples use synthetic resource IDs; replace them with resources accessible to your account. Required fields and defaults describe the API contract, while account access, available credits, and supported setting combinations are checked when an operation runs.

Make your first request

Obtain an APOB API key through your signed-in APOB integration. Send the complete key in Authorization: Bearer <APOB_API_KEY> on every authenticated request. See authentication for key management and the separate Firebase login flow.
cURL

Request and response format

The response contains data, errors, or both. Read the GraphQL errors array even when HTTP returns 200. A mutation can create a resource before a selected response field fails, so an error does not always prove that submission failed.

Call from JavaScript

This helper accepts an already obtained APOB API key. It performs one HTTP request and reports HTTP or GraphQL errors without automatically retrying.
JavaScript

Complete a generation

1

Discover inputs

Read your account, choose an accessible ready model, and select models and elements.
2

Submit once

Use the image, video, or speech mutation and retain the returned content ID and task ID. Generation mutations can consume credits.
3

Poll the existing content

Read the task and results until the task finishes. Success requires both status: finished and finishCode: 0.
4

Download outputs

Select the returned media IDs and request download URLs. Refresh an expired URL by reading the same result again.
Do not automatically resubmit a generation after a timeout, connection loss, or partial GraphQL response. Reconcile the existing content or account history first; a second mutation can start and charge for a separate generation.
For authentication and operation failures, see errors.