--- title: "How to Integrate the Mariana Tek API (2026)" canonical: "https://aifitnessapi.com/integrate/mariana-tek-api" cluster: "Integration Guides" primary_query: "how to integrate the Mariana Tek API" last_reviewed: "2026-10-17" description: "Integrate Mariana Tek's Admin and Customer APIs: credentials from its Integrations team, OAuth with PKCE or API keys, sandbox tenants and technical review." publisher: "AIFitnessAPI — independent, not sponsored" cite_as: "\"How to Integrate the Mariana Tek API (2026)\", AIFitnessAPI, https://aifitnessapi.com/integrate/mariana-tek-api" --- # How to Integrate the Mariana Tek API (2026) > Mariana Tek issues API credentials through its Integrations team rather than an open sign-up form: you contact integrations@marianatek.com to register an application, build against a sandbox tenant, and may need to pass a technical review that Mariana Tek says can take up to 1 to 3 weeks before you go live with a studio. Requests use bearer authentication, with either an OAuth 2.0 access token from the Authorization Code flow on the studio's own subdomain, adding PKCE for single-page and mobile apps, or an API key tied to your application's service account for server-side work. Webhooks are switched on by request, and production webhooks for a studio need the studio owner's approval by email. - Canonical: https://aifitnessapi.com/integrate/mariana-tek-api - Last reviewed: 2026-10-17 - Publisher: AIFitnessAPI (https://aifitnessapi.com) — independent, not sponsored - Cite as: "How to Integrate the Mariana Tek API (2026)", AIFitnessAPI, https://aifitnessapi.com/integrate/mariana-tek-api --- Mariana Tek sells boutique fitness software to studios and franchises, and publishes a family of APIs for the developers who build around it. This guide is written from Mariana Tek's developer guides at guides.marianatek.com and its Customer API OpenAPI document as they stood on October 17, 2026. Still choosing a platform? Our [gym and studio management software API comparison](/fitness-apis/gym-management-software-apis) puts Mariana Tek next to Mindbody, TeamUp, Wodify and ABC Glofox. ## Which Mariana Tek API you need Mariana Tek's API overview lists seven surfaces: | API | What Mariana Tek says it is for | |---|---| | Admin API | Its primary API, the control arm for backend and business needs; tools for fitness business administration | | Customer API | Bespoke customer experiences, built from the customer's perspective | | Studio API | Endpoints to manage studio configurations | | MT Stripe API | A custom checkout flow on Mariana Tek's Stripe integration | | Documents API | Waivers, documents and contracts | | Pricing API | Pricing control | | Webhooks | Notifications about account events | Its "ways to build" page maps them to projects. Custom development for a studio's website uses the pre-built Web Integrations, the Customer API, or both. A studio app that helps owners run the business extends the Admin Application with the Admin API, and can use the Pricing Engine to change class prices dynamically. A customer app used by one or many studios combines the Customer API with Universal Authentication. A booking app that partners with many studios uses Bypass Bookings. The Customer API is described in an OpenAPI document at `https://docs.marianatek.com/api/customer/v1/schema/`, which Mariana Tek introduces as giving you "the power to build custom booking and buying experiences for fitness customers". Generate a client from it rather than hand-writing request types. ## Access: through Mariana Tek's Integrations team There is no public sign-up form in the guides we read. To register an application and get OAuth credentials, the credentials guide says to contact `integrations@marianatek.com`, and the same address manages API keys. Mariana Tek's FAQ describes a Developer Portal for managing sandbox integrations, generating credentials and starting a technical review, but says it is in Beta and not uniformly available yet. You build against a **sandbox**: a mock studio seeded with sample data, with its own tenant name, sandbox API and Web Integrations, almost identical to production. Every studio, live or sandbox, is addressed by its tenant name (the MT subdomain), and the sandbox API lives at `https://{tenant_name}.marianatek.com/api`. Sandbox tenant names often end in `.sandbox`. Integration partners get access to their sandbox Admin App during onboarding. ## Credentials: OAuth or an API key Mariana Tek accepts two kinds of credential, and both are sent with bearer authentication: - **OAuth 2.0 client credentials**, when requests should act for an end user: apps that need a studio owner or customer to log in, user-scoped views and profiles, or single sign-on. Single-page and mobile apps must use OAuth. - **An API key**, tied to a service account for your application, when you manipulate data for many users without any one user's login. You choose the service user's permissions when you register, and keys belong only on a server: Mariana Tek says never to commit them to version control or use them in client-side code. ```bash curl -H "Authorization: Bearer YOUR_API_KEY_OR_ACCESS_TOKEN" \ "https://YOUR_TENANT.marianatek.com/api/users/self" ``` ## The OAuth flow, on the studio's subdomain Mariana Tek supports the Authorization Code flow for confidential clients, such as server-side web apps, and the Authorization Code flow with PKCE for public clients, such as single-page and mobile apps. Both run on the brand's own subdomain: ```text GET https://{SUBDOMAIN}.marianatek.com/o/authorize ?response_type=code&client_id=...&redirect_uri=...&state=... (PKCE adds code_challenge and code_challenge_method=S256) POST https://{SUBDOMAIN}.marianatek.com/o/token/ grant_type=authorization_code, client_id, code, redirect_uri, plus client_secret (Authorization Code) or code_verifier (PKCE) ``` Details from the guide: - `state` is required, and Mariana Tek tells you to check it on the callback to prevent CSRF. - `prompt=True` forces a login even when the user already has a session. Without it, a user with an active session is sent straight back to your `redirect_uri`. - The example token response has `expires_in` of 604800 seconds, which is seven days, along with a `refresh_token`. Exchange it with `grant_type=refresh_token`; confidential clients also send their `client_secret`. - The redirect URL must match the registered one exactly. Mariana Tek's FAQ lists the usual causes of a mismatch error: no redirect URL registered yet, a typo, a trailing backslash on only one of the two URLs, URL encoding, or an old URL still registered. The [OAuth explainer](/learn/what-is-oauth-for-health-data) covers why public clients need PKCE. ## Webhooks are enabled on request Mariana Tek can post events to your URL, for example when a customer creates an account, makes a reservation or checks in to class. There is no self-serve subscription in the guides: you ask Integrations, giving your HTTPS subscriber URL, the events you want and the environment. For a studio's production environment, Integrations needs the studio owner's approval by email. One design rule matters if you plan to serve many studios. Mariana Tek calls an integration that can be switched on for a new studio from one bundle of credentials a one-click-install, and for webhooks that requires subscriber URLs that are identical across clients or differ only by the MT subdomain. Build the subdomain into your URL path from day one. ## Technical review before going live Before going live with a studio, you may have to pass a technical review; Mariana Tek says not every app needs one. The integration must be fully built and tested in the sandbox first. The submission covers how the integration works, the endpoints and webhooks it uses, credentialed access to a test environment, a screen recording, and the studios you work with or plan to. Mariana Tek says reviews "can take up to 1-3 weeks to complete". Two consequences of approval to plan for: - **Scoped access.** Your account permissions are limited to the endpoints and use cases that were reviewed and approved, and using other endpoints you can reach is not permitted. - **Ongoing standing.** If a launched integration falls outside the approved guidelines, Mariana Tek discontinues its API access until you work through a consultation with your integration manager. ## What we could not find Neither rate limits nor API pricing appear in the guides we read, and the Admin API reference was not among the pages we fetched. Ask Integrations about both before you size a production rollout. Mariana Tek also lists its existing partners in a marketplace at partners.marianatek.com, including ClassPass, Wellhub and Spivi, which is a quick way to see which kinds of integrations it already approves. The rest of the cluster is at [how to integrate a fitness or health API](/integrate). ## Sources - [guides.marianatek.com/api-overview](https://guides.marianatek.com/api-overview) — The Admin, Customer, Studio, MT Stripe, Documents and Pricing APIs and Webhooks. (checked 2026-10-17) - [guides.marianatek.com/ways-to-build](https://guides.marianatek.com/ways-to-build) — Which APIs fit studio websites, studio apps, customer apps and booking apps. (checked 2026-10-17) - [docs.marianatek.com/api/customer/v1/schema/](https://docs.marianatek.com/api/customer/v1/schema/) — Customer API OpenAPI document and its description. (checked 2026-10-17) - [guides.marianatek.com/credentials](https://guides.marianatek.com/credentials) — OAuth versus API keys, registering through Integrations, bearer authentication, key handling. (checked 2026-10-17) - [guides.marianatek.com/auth](https://guides.marianatek.com/auth) — Authorization Code and PKCE flows, parameters, token response and refresh tokens. (checked 2026-10-17) - [guides.marianatek.com/faqs](https://guides.marianatek.com/faqs) — Sandbox, Developer Portal (Beta), tenant name, one-click-install, credential choice, redirect mismatch errors, webhook setup. (checked 2026-10-17) - [guides.marianatek.com/webhooks](https://guides.marianatek.com/webhooks) — What webhooks deliver and that they start through Integrations. (checked 2026-10-17) - [guides.marianatek.com/integration-review](https://guides.marianatek.com/integration-review) — Technical review requirements, 1-3 week timeframe, scoped permissions and loss of access. (checked 2026-10-17) - [partners.marianatek.com/](https://partners.marianatek.com/) — Partner marketplace listings including ClassPass, Wellhub and Spivi. (checked 2026-10-17) - [www.marianatek.com/](https://www.marianatek.com/) — Mariana Tek's description of its boutique fitness software. (checked 2026-10-17) ## FAQ ### How do I get Mariana Tek API credentials? Contact Mariana Tek's Integrations team at integrations@marianatek.com to register your application and receive OAuth client credentials or an API key; its guides do not describe an open sign-up form. Mariana Tek's FAQ mentions a self-service Developer Portal for managing sandbox integrations and credentials, but says it is in Beta and not uniformly available yet. [Permalink](https://aifitnessapi.com/integrate/mariana-tek-api#faq-1) ### Should a Mariana Tek integration use OAuth or an API key? Use OAuth when a studio owner or customer logs in, for user-scoped views and profiles, or for single sign-on; single-page and mobile apps must use OAuth. Use an API key, tied to your application's service account, for server-side data work across many users with no individual login. Both are sent as bearer tokens, and Mariana Tek says API keys must never be committed to version control or used client-side. [Permalink](https://aifitnessapi.com/integrate/mariana-tek-api#faq-2) ### How long does Mariana Tek's technical review take? Mariana Tek says reviews can take up to 1-3 weeks to complete, and not every app needs one. Submit only a fully built integration tested in the sandbox, with a description, the endpoints and webhooks it uses, test-environment logins, a screen recording and the studios you work with. After approval, your permissions are scoped to the endpoints and use cases that were approved. [Permalink](https://aifitnessapi.com/integrate/mariana-tek-api#faq-3) ### How do I turn on Mariana Tek webhooks? Ask Mariana Tek's Integrations team for a webhooks subscription, giving your HTTPS subscriber URL, the events you want and the environment, sandbox or production. For a studio's production environment, the studio owner must send approval to Integrations by email. To stay a one-click-install, keep subscriber URLs identical across studios or differing only by the MT subdomain. [Permalink](https://aifitnessapi.com/integrate/mariana-tek-api#faq-4) ### What is a Mariana Tek tenant name? It is the MT subdomain that identifies a live studio or a sandbox, and you need it to call the API and set up Web Integrations; the sandbox API lives at your tenant name followed by .marianatek.com/api. Sandbox tenant names often end in .sandbox, and you receive yours once you are set up as a developer with Mariana Tek. [Permalink](https://aifitnessapi.com/integrate/mariana-tek-api#faq-5)