Blue Reacher
OpenAPI spec and Postman21 / 50

OpenAPI spec and Postman

Download the machine-readable API spec, import it into Postman or Insomnia, and generate a typed client in any language.

The spec

The Blue Reacher API is published as an OpenAPI 3.1 document:

https://docs.bluereacher.com/openapi.json

It covers the full API surface: messages and group sends, voice memos, conversations and groups, lines, delivery status, signals (tapbacks, typing, read state), contacts, opt-out, AI assistant control, capability lookup, usage metering, the MCP endpoint, and every webhook event, with request and response schemas, the auth scheme, and the error codes each endpoint returns. The spec, these prose pages, and the live API are generated against the same contract; a disagreement between them is a bug, and we want to hear about it.

Import into Postman

  1. Postman, Import, Link.
  2. Paste https://docs.bluereacher.com/openapi.json, Continue, Import.
  3. Postman generates a collection with every endpoint and an example body per request.
  4. Open the collection's Authorization tab, type Bearer Token, and paste your key. Every request inherits it.

Set the collection variable baseUrl to https://api.bluereacher.com if your Postman version does not pick up the server block automatically; paths in the spec carry the /v1 prefix.

Import into Insomnia or Bruno

Both accept the same URL. Insomnia: Create, Import From, URL. Bruno: Import Collection, OpenAPI. Auth setup is identical, a bearer token at collection level.

Generate a client

# TypeScript
npx openapi-typescript https://docs.bluereacher.com/openapi.json -o bluereacher.d.ts

# Python
openapi-python-client generate --url https://docs.bluereacher.com/openapi.json

# Go, Java, Ruby, PHP, and others
openapi-generator-cli generate \
  -i https://docs.bluereacher.com/openapi.json \
  -g go \
  -o ./bluereacher-go

A generated client gives you types and request shapes, not judgment. The rules that keep a program working, an Idempotency-Key on every send, capacity awareness before a batch, signature verification on every webhook, are behavioral and live in key concepts, rate limits, and webhooks.

For AI agents and assistants

The whole documentation set is available in machine-readable form:

https://docs.bluereacher.com/llms.txt        # index
https://docs.bluereacher.com/llms-full.txt   # every page, full text

Any page also returns markdown when you request it with a .md suffix, so https://docs.bluereacher.com/docs/guides/quickstart.md gives the raw source instead of the rendered page.

If you want an assistant operating the account rather than reading about it, use the MCP server, which exposes the same operations as tools.

Keeping in sync

The spec is versioned with the documentation and updated alongside it. Pin a copy in your repository if reproducible builds matter to you, and diff against the live URL when you upgrade rather than regenerating blind.

On this page