For developers & agents
Machine-legible surveys, on purpose
Surveymatic is built so software can use it, not only people clicking through. You can create surveys, launch them, collect responses with AI follow-ups, and read solid-response results in code, on the same plan limits a person gets.
What the API offers
REST API with OpenAPI 3.1
It's the same API the app uses, documented with a generated OpenAPI 3.1 spec. Read the reference, download the machine-readable document, and generate a client in a few minutes.
Scoped API keys
Create a key for this workspace with only the scopes an integration needs: surveys:read, surveys:write, responses:read, and responses:write. responses:read can fetch results. If you want to change whether a response is included, the key needs responses:write. Keys that already had surveys:write keep that ability. We hash keys at rest, show each one once, and they expire after a year by default. Each workspace shares one rate limit: 60 requests a minute and 5 active keys on Growth, 300 requests a minute and 25 active keys on Pro. Billing always stays with a person.
MCP server, Streamable HTTP
Point any MCP client at one endpoint and use the same API key. There's no second credential, and no OAuth step. The tools cover the full loop: create a survey, request a launch, draft email invites, read solid-response results, ask a question, and sign a certificate. A person approves the launch unless the workspace is set to Per API key and that key was given launch permission. Agents can't send invites. The live-survey limit is the same one a person on the plan hits.
Agent discovery built in
An A2A agent card lives at /.well-known/agent-card.json. Evaluators and orchestrators can find the API, see what it can do, and check the claims in code instead of taking the marketing page's word for it.
A person approves the launch.
Every survey an agent creates starts as a draft. By default each launch waits for a person to approve or decline it. An admin can switch Allow approvals to Per API key, and then only a key that was given launch permission when it was created can publish without that extra click. Agents can draft email invites. A person always sends them. Agent usage still meters against the same plan limits as a person.
Get started in three steps
1
Create a scoped key
API keys are on Growth and Pro. Open the API page and create a key with just the scopes you need. You'll see it once, so store it somewhere safe. On Free, you'll get an upgrade path instead of a key.
2
Read the docs
The reference covers every endpoint and the scopes each one needs. The OpenAPI document is generated from the same schemas that check requests, so it can't drift from the API.
3
Connect your agent
Use the key as a Bearer token on the REST API, or point an MCP client at /api/mcp. request_launch and launch_survey ask a person to publish. draft_invites saves an email that a person sends.