Developers

Automate Bidama

Use the REST API with a scoped API key, or connect an AI agent to the remote MCP server with OAuth. Both work on the same account data with the same limits.

Getting started

For the REST API, sign in and create a key on the API keys page. Copy it right away, because Bidama shows the full key only once.
Give the key the scopes it needs: read for listing and analytics, write to create and edit, and delete to remove things.
Call the REST API under /api/v1/, or point ChatGPT, Claude, or any other remote MCP client at /mcp and sign in with OAuth.

Pick a surface

REST API Every endpoint with its scope, request shape, and error codes, plus the OpenAPI download. MCP MCP How to connect an agent over OAuth, and what each of the four tools can do.

Shared rules

You only ever see and change your own resources. Another account's resources are off limits, whichever surface you use.
Errors come back as JSON with a stable error_code. When you hit a rate limit you get 429 and a Retry-After header.
To avoid overwriting someone else's edit, read the resource first and send its revision back with your change: X-Resource-If-Match in REST, if_match in MCP.