Developer docs
There are two sides to a DeploTeka integration. Your backend receives each client store’s credentials. Your tools read your workspace and check access to client stores.
Receive credentials in your backend
Fleet contract
For a Shopify app with code. Two routes in your app: DeploTeka registers each store’s app credentials and reads back install proof.
Token delivery
For a service that calls the Admin API. One route: DeploTeka sends each merchant’s Admin API token after install, and tells you on uninstall.
Work with your workspace
REST API
Read apps, stores and releases. Check and request collaborator access to a client store.
MCP for AI tools
The same reads and checks from Claude, Cursor or any MCP client.
CLI
npx deploteka prepares your app, connects your workspace and runs releases from a terminal.
Examples
Working code for the common jobs: syncing stores, checking access, receiving tokens, releasing from CI.
The API and MCP need a key from your workspace. Set up workspace inventory to read apps, stores and releases; it works before you connect Shopify. Set up Shopify access to check and request access to client stores. New to DeploTeka? Create a workspace first.
Which do I need?
| You have | You need |
|---|---|
| A Shopify app with code: embedded, with extensions, or both | Fleet contract and the CLI, which adds it for you on Remix and React Router |
| A service on your own servers that calls the Admin API | Token delivery |
| Scripts, a CRM or an AI assistant that should know your fleet | The REST API or MCP |
Not available yet
Creating an app or starting a store setup through the API is not available. Do both in the cabinet or with the CLI. The API and MCP read your workspace and handle collaborator access.