API Reference

The Invoker HTTP API lets you manage deployments, retrieve submissions, and configure webhooks programmatically. This is the same API that the MCP server calls under the hood.

Base URL

https://api.invoker.page

Authentication

All endpoints except form submission (POST /submit/:id) require a valid API key in the Authorization header:

Authorization: Bearer inv_xxxxx

See Authentication for details on obtaining and managing API keys.

Content type

All request and response bodies are JSON unless otherwise noted:

Content-Type: application/json

The form submission endpoint (POST /submit/:id) also accepts application/x-www-form-urlencoded and multipart/form-data.

Endpoints

Deployments

Method	Path	Description
POST	/deploy	Create a new deployment
GET	/deploy/:id	Get deployment status
PUT	/deploy/:id	Update deployment HTML
PATCH	/deploy/:id	Update deployment settings
DELETE	/deploy/:id	Delete a deployment

Submissions

Method	Path	Description
POST	/submit/:deployId	Submit a form (public, no auth)
GET	/submissions/:deployId	List submissions for a deployment

Webhooks

Method	Path	Description
POST	/webhooks/:deployId	Create a webhook
GET	/webhooks/:deployId	List webhooks for a deployment
DELETE	/webhooks/:deployId/:webhookId	Delete a webhook

Error handling

All error responses return a JSON object with an error field:

{ "error": "description of what went wrong" }

See Errors & Rate Limits for the full list of status codes and rate limit details.

Using the MCP server instead?

You don't need to call this API directly. The MCP tools wrap every endpoint and handle authentication automatically. This reference is for direct HTTP integration.