API
API overview
Drive Nubu from your own software: assets, templates, flow runs, renders and deliveries.
The Nubu API lets your own software manage the asset library, upload templates, trigger flows and collect finished renders without anyone opening Nubu. It is part of the Business+ plan.
What you can do
- Upload, edit, replace and delete assets in the library, exactly as the Assets page does.
- Upload template packages exported from the Nubu Builder.
- Trigger a flow that contains an API Trigger node, then follow the run as its creatives are built, approved and rendered.
- Approve, re-render, download and delete creatives.
- Receive the finished render in your own system through an API Request node, and a callback every time a run changes state.
The basics
- Base URL:
https://app.nubu.app/api/v1 - Every request carries
Authorization: Bearer nubu_api_...(see Authentication and keys). - Requests and responses are JSON (
Content-Type: application/json). File bytes never travel through the API itself: they go straight to storage through the upload URLs the API hands you. - Every response carries an
X-Request-Idheader. Quote it when you contact support. Send your ownX-Request-Id(letters, digits,.,_,:and-, up to 128 characters) and it is echoed back. - Lists are paged: pass
limit(default 50, at most 200) and, for the next page, thenext_cursorof the previous answer ascursor.next_cursorisnullon the last page. - Query strings and bodies are strict: an unknown parameter or field answers
422 validation_failed, so a typo never silently does nothing. - Dates are ISO 8601 in UTC. Ids are UUIDs.
A typical integration
- Upload the source files as assets, into folders if you organise them that way, and keep the asset ids (Uploading assets, Folders).
- Call the flow's trigger with your values and asset ids (Triggering a flow).
- Poll the run, or let a callback tell you (Runs and creatives, Callbacks).
- Collect the renders: an API Request node delivers them to your endpoint (API Request delivery), or download them with the API.
Nothing about the API bypasses Nubu: the files become normal library assets, the flow's own logic builds the creatives, the usual review and render steps apply, and the renders stay stored in Nubu.