# Bubble

Plan API Connector inputs and stable result references for a low-code application.

## Use API Connector for outbound requests

Bubble's [API Connector manual](https://manual.bubble.io/help-guides/integrations/api/the-api-connector) describes connecting an application to external APIs and using responses as data or actions. Plan the connection around the actual SeedRouter request and response format.

## Define the calls

For an image workflow, define one call that submits a task and another that retrieves its status. Use the [API quickstart](https://seedrouter.ai/docs/api/quickstart) and [task reference](https://seedrouter.ai/docs/api/tasks) as the source for URLs, authentication and fields. Keep the API credential private and server-side; do not place it in an input that becomes visible to application users.

When initializing a call, remember that a real generation request can spend credits. Use an explicitly approved test and retain its response for field mapping.

## Keep a stable application record

Store your own record identifier, the task `id`, current state and completed output together. Subsequent workflow steps should reference those fields. Do not build the application around a generated identifier being used as a permanent JSON property name.

Check what happens when the user revisits the page, starts another request or receives a late result. Opening an existing output should read the saved application record rather than submit another generation.

## Scope the integration

[Game scene illustrations](https://seedrouter.ai/solutions/game-scene-generation) are one possible application. Your Bubble workflows control user access, records, refresh behavior and display; SeedRouter supplies the selected model API.

Music generation is a future capability in SeedRouter. Historical examples of music APIs in low-code tools establish integration questions, not the availability or current response format of a SeedRouter music endpoint.

The API Connector reference was checked on October 12, 2026. This guide defines the connection pattern; it does not report a newly executed Bubble application test.
