Bubbl Platform API

vv1

A public REST API for your own systems and no-code tools (Zapier, Make, n8n) — separate from Bubbl's device/SDK API, and with no company or user management of its own.

Get a token from Configuration › Platform API in the dashboard, then send it as Authorization: Bearer bubbl_…. A Sandbox token works immediately and every scope it was issued with is available; a Production token only has reports:read until Bubbl's customer services turns the rest on for your workspace.

Lists are cursor-paginated (?cursor=&limit=, newest first) and take ?updated_since= for polling. Errors always come back as {"error": {"code", "message", "fields"?}}.

Base URLs#

https://api.bubbl.tech/platform/v1

Production. Only reports:read works until customer services enable the Platform API for your workspace.

https://api.sandbox.bubbl.tech/platform/v1

Sandbox. Every ability works, with lower rate limits: 30 requests and 10 writes a minute, 1,000 requests a day.

Resources#

Workspace

The workspace, environment and abilities of the token you're using.

GET/meGet the current token

Locations

Places a campaign can target — a circle or a polygon. A location is only ever created by importing a GeoJSON FeatureCollection (see the import endpoint); this resource lists, reads, updates and deletes ones already imported.

Campaigns

When and to whom your notifications go out. A geo campaign targets locations (directly or via location groups) and fires when a device enters or leaves one; a push campaign sends at fixed times to an audience of segments (or everyone). Notifications are added afterwards — see Notifications, nested under a campaign.

Notifications

A campaign's notifications — nested under it, since a notification has no meaning until a campaign decides when it fires. Creating one here writes its content (headline, body, media, CTA, survey questions) and its trigger together; there's no separate endpoint for notification content alone.