Skip to main content
The API creates one Brand Skill resource for each accepted request. Keep its ID in your own job record from creation through deletion.

Create once and retain the ID

Submit brand source material to POST /brand-skills. Bloom accepts the source, starts processing asynchronously, and returns 202 Accepted with the Brand Skill ID. Persist that ID before starting any later step. Use it for polling, deletion, and support.

Poll the same resource

Call GET /brand-skills/{id} until the status is completed or failed. Start with a five-second polling interval and back off between subsequent requests. If the API returns 429 Too Many Requests, pause before retrying. The Get a Brand Skill reference owns the exact lifecycle states and response fields.

Store the result before cleanup

A completed resource includes a temporary URL for its self-contained ZIP. Download it promptly and store or extract it in your own system before deleting the Bloom resource. See Use the downloaded Skill for the folder contract. If the build fails, retain the Brand Skill ID and the returned failure details. Include the ID when contacting Bloom. Do not share the source URL or API key.

Delete Bloom’s retained copy

After your system has stored the completed Skill or recorded a failure, call DELETE /brand-skills/{id}. Deletion cancels active work when possible and removes Bloom’s stored sources, generated ZIP, and Brand Skill resource. The Delete a Brand Skill reference contains the exact response and error definitions.