Stape API overview

The Stape API lets you manage your Stape account and server-side tracking infrastructure programmatically. It’s a REST API, with interactive reference for each location:

• Global API reference
• EU API reference

Requests are authorized with an account API key in a header. Container-level API keys are also available in container settings for specific app identifications and CRM webhooks.

With the Stape API you can:

• Manage accounts – edit settings (change email, password, billing info, 2FA), convert to an agency, manage invoices, notifications, and delete account
• Manage CAPI Gateways – create, edit, delete
• Manage containers – change plan, cancel/reactivate subscription, enable/disable power-ups, manage domains and DNS, access logs, and view daily/domain request statistics
• Manage partners – add sub-users, view commission/payment statistics, and set up or edit payout schedules

For the instructions on how to use Stape API, read How to use Stape API. 

Stape API Global and Stape API EU provide the exact same functionality and endpoints, but target two completely isolated regional environments and database clusters.

API keys generated in a Global account only work in the Global reference, and EU account keys will work only in the EU reference. Sending a key to the other location returns a 400 error. 

The accounts managed through the Stape API EU are billed in EUR and subject to EU VAT rules. The accounts managed through the Stape API Global are billed in USD or EUR depending on the country.

For more information about Global and EU accounts read EU vs Global.

The Stape MCP server acts as a bridge between AI assistants and the Stape REST API. MCP unlocks the endpoints as interactive tools that AI clients (like Claude Desktop, Cursor, VS Code, and Copilot) can call on their own.

Simply describe what you need in a natural language – whether that's fetching your sGTM containers or creating a new one. Your AI assistant automatically selects the relevant MCP tool, sends the request through the server to the REST API, and delivers the result directly into your chat window. No cURL commands or manual HTTP request building required.

There’s no extra login process, just supply your standard Stape API key when setting up your client, and the server will securely authenticate API calls on your behalf.

Regional handling works identically to the REST API: requests default to Stape API Global, but you can route traffic to the EU location by including the X-Stape-Region: EU header.

For the instructions on how to use the MCP Server, read How to set up the Model Context Protocol (MCP) server for Stape.

1. 1.
   Automated Custom Loader deployment across multiple domains. For organizations managing dozens of sites that require features like Custom Loader and Cookie Keeper, manually generating power-up snippets in the Stape admin panel isn’t efficient. Using the API, you can programmatically fetch the appropriate script for each domain and dynamically inject it through your deployment pipeline.
2. 2.
   Bulk custom domain setup and DNS revalidation. Configuring tagging subdomains across a large network of websites can be tedious when done manually. The API allows you to setup custom domains and trigger DNS revalidation automatically, ensuring records stay synchronized without navigating through individual container settings.
3. 3.
   Proactive usage and plan monitoring. Instead of manually inspecting every container to check monthly request limits, you can pull plan details, usage statistics, and billing metrics through the API to feed directly into your custom dashboards or automated alert systems.