Skip to main content

API Basics

Short answer

Authenticate with header TestChimp-Api-Key (project key from Project Settings → Key management). Call POST https://featureservice.testchimp.io/api/mcp/... with Content-Type: application/json. Bodies use protobuf JSON: camelCase fields and string enum names. Project scope comes from the key — never send org or project ids as client credentials.

Base URL​

EnvironmentBase URL
Productionhttps://featureservice.testchimp.io
Override (CLI/MCP)TESTCHIMP_BACKEND_URL (no trailing slash)

All documented operations are under /api/mcp/.

Authentication​

ItemValue
HeaderTestChimp-Api-Key: <project-api-key>
CLI / MCP envTESTCHIMP_API_KEY
Where to createProject Settings → Key management

Missing or invalid keys return 401. The project is resolved server-side from the key.

Do not send:

  • Project-Id as a substitute for the API key (ignored when it disagrees with the key)
  • Organization-Id — not a public integration input

Request conventions​

  • Method: POST only
  • Content-Type: application/json
  • Empty body endpoints accept {}
  • Field names: camelCase (protobuf JSON / JsonFormat)
  • Enums: string names (e.g. "ACTIVE", not integers)
  • 64-bit integers may appear as JSON strings

Errors​

StatusMeaning
401Missing or invalid API key
400Validation / business error (message in body)

Minimal example​

curl -sS -X POST "https://featureservice.testchimp.io/api/mcp/list_rum_environments" \
  -H "Content-Type: application/json" \
  -H "TestChimp-Api-Key: $TESTCHIMP_API_KEY" \
  -d '{}'

Interactive reference​

Open the API Reference for per-endpoint schemas, examples, and the Scalar playground. Paste your project API key into the auth field to try non-mutating calls against your project.

CLI and MCP​

The same endpoints power @testchimp/cli and the TestChimp MCP server. Tool names are kebab-case (e.g. get-release-details → POST /api/mcp/get_release_details).

Frequently asked questions

How do I authenticate?

Send header TestChimp-Api-Key with your project API key. Project scope is resolved from the key.

What is the base URL?

Production is https://featureservice.testchimp.io. Override with TESTCHIMP_BACKEND_URL for CLI/MCP.

Do I need Organization-Id or Project-Id headers?

No. Those are not public integration inputs for /api/mcp APIs.

Related pages