Developers

GrowSurf developer resources

One REST API, at a predictable address. The SDKs, the CLI, and the MCP server are interfaces over it — every one of them ends up calling the same endpoints you can call yourself.

Your first request

# Every endpoint except POST /accounts takes an API key
curl https://api.growsurf.com/v2/campaigns \
  -H "Authorization: Bearer $GROWSURF_API_KEY"

GrowSurf REST API

The universal surface. Create and manage teams, programs, participants, referrals, and rewards from your own server. Every endpoint except POST /accounts takes an API key in an Authorization: Bearer header, and you create and scope keys in GrowSurf Settings.

REST API documentation — endpoint reference and guides
Authentication — how to get and present an API key
API lifecycle, versioning, and deprecation policy
Webhooks — subscribe to referral and reward events

Base URL

https://api.growsurf.com/v2

GrowSurf OpenAPI spec

The machine-readable contract for the REST API, in OpenAPI 3.1, generated from the same source the API runs on and served same-origin so a client never has to guess a location. No API key is needed to read it.

OpenAPI spec page — every fetch location, scopes, and code generation
arazzo.yaml — the Arazzo 1.1 onboarding workflow

Spec

growsurf.com/openapi.json growsurf.com/openapi.yaml

GrowSurf MCP server

Connect an AI assistant to GrowSurf over the Model Context Protocol. The hosted server authenticates with OAuth, so your assistant never handles an API key; the same tools also run locally over stdio. It is an interface over the REST API, not a separate product — if your assistant can send HTTPS requests, you do not need it.