UGCBloom Logo MarkUGCBloom Wordmark

Platform · v1

Build with UGCBloom.

UGCBloom runs influencer campaigns end-to-end: recruiting creators, briefing them, paying them per video or per conversion, and attributing every sale back to the right creator. This page covers the two surfaces you'll use as a developer: the REST API for reading data out of UGCBloom, and the tracking pixel you embed on your website to attribute clicks and conversions to specific creators.

UGCBloom API: REST endpoints under https://ugcbloom.com/api/v1 for reading campaigns, creators, videos, stats, and messages. A separate tracking surface at https://ugcbloom.com/api/script.js, /api/promolink, /api/event handles referral tracking on brand-owned sites. Auth: Bearer ugcb_live_... for REST; tracking endpoints are anonymous, scoped by org id passed via data-org. OpenAPI spec at /openapi.json. MCP server at /api/mcp (see /docs/api/agents).

REST base
https://ugcbloom.com/api/v1
Pixel base
https://ugcbloom.com/api/
Auth
Bearer API key for REST. The pixel surface is public, scoped by your org id.
Rate limit
100 req/min per API key · 120 req/min per IP on pixel endpoints.

Building with AI agents?

Skip the REST plumbing entirely. Claude, ChatGPT, and other agents connect to UGCBloom directly through our MCP server. OAuth handshake, no API key copy-pasting, full read access out of the box.

Where to next