Adapty server-side API

Name: Adapty server-side API API
Brand: Adapty server-side API
Availability: InStock

★ Only Publicly Available SpecPaymentsBilling SubscriptionsapiKey16 EndpointsREST

For Agents

Manage Adapty user profiles, grant or revoke paid access levels, validate purchases, and configure refund-handling — used by backend systems to keep entitlement state in sync with Adapty.

Quickstart

Get started with Adapty server-side API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"grant a paid access level to an adapty user"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Adapty server-side API API.

Create, read, update, and delete Adapty user profiles by customer user ID

Grant or revoke specific paid access levels on a profile to override store-driven entitlements

Set transaction records on a profile for cross-platform purchase reconciliation

Validate Stripe purchase tokens and link the resulting subscription to a profile

GET STARTED

Start building with Adapty server-side API API

Explore with Jentic

View OpenAPI Spec

Use for: Create an Adapty profile for a newly signed-up user, Grant a 'premium' access level to a user after a manual concession, Revoke premium access from a user who issued a chargeback, Validate a Stripe purchase token and attach it to an Adapty profile

Not supported: Does not handle App Store or Google Play receipt validation, paywall configuration, or in-app SDK events — use for backend profile and entitlement management only.

Jentic publishes the only available OpenAPI specification for Adapty server-side API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Adapty server-side API, keeping it validated and agent-ready. Adapty is a mobile subscription and in-app-purchase platform; the server-side API lets backend systems manage user profiles, grant or revoke paid access levels, validate Stripe transactions, and configure the Refund Saver feature. It is the sync surface for keeping a backend in agreement with Adapty's source-of-truth on entitlement state across iOS, Android, and web purchases. Authentication uses a secret API key passed in the Authorization header.

Use Cases

Patterns agents use Adapty server-side API API for, with concrete tasks.

★ Granting concessions and overrides

Customer support agents need to grant temporary or permanent paid access without going through the App Store or Google Play. The Adapty server-side API exposes /purchase/profile/grant/access-level/ and /purchase/profile/revoke/access-level/ so an agent can apply a concession in seconds and have it reflected on the user's mobile app the next time they fetch profile data. This avoids manual database edits and keeps Adapty as the entitlement source of truth.

Call POST /api/v2/server-side-api/purchase/profile/grant/access-level/ with customer_user_id, access_level_id 'premium', and a 7-day expiration to comp a frustrated user.

Stripe web purchase reconciliation

Apps that sell subscriptions on the web via Stripe and on mobile via Apple/Google need a single place to reason about entitlements. The /sdk/purchase/stripe/token/validate/ endpoint accepts a Stripe token, verifies it server-side, and links the resulting subscription to an Adapty profile so mobile clients see the user as paid. This keeps cross-platform users from re-paying when they switch devices.

POST /api/v1/sdk/purchase/stripe/token/validate/ with the Stripe checkout session's token and the matching customer_user_id to attach the web subscription to the user's Adapty profile.

Profile lifecycle in a CRM workflow

Marketing operations want every signed-up user to exist as an Adapty profile so behavioural data and access-level changes flow into segmentation. Backend agents call /server-side-api/profile/ on signup to create the profile, GET it before sending churn emails, and DELETE it on account closure to honour deletion requests — all without touching the mobile SDK.

POST /api/v2/server-side-api/profile/ with customer_user_id and email at signup; later call DELETE on the same path on account closure.

AI agent for support concessions via Jentic

A support automation built on Jentic discovers Adapty's grant and revoke operations through a search like 'grant subscription access to a user'. The agent fills in customer_user_id and access_level_id from the support ticket, executes the call through Jentic, and the access change is live before the user closes the chat. Jentic's MAXsystem holds the secret API key so it never appears in agent context.

Use Jentic to search 'grant adapty access level', load the schema, and execute with customer_user_id and access_level_id 'pro' for a user reporting a billing issue.

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for adapty server-side api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v2/server-side-api/profile/

Create profile

GET

/api/v2/server-side-api/profile/

Get profile

PATCH

/api/v2/server-side-api/profile/

Update profile

DELETE

/api/v2/server-side-api/profile/

Delete profile

POST

/api/v2/server-side-api/purchase/profile/grant/access-level/

Grant access level

POST

/api/v2/server-side-api/purchase/profile/revoke/access-level/

Revoke access level

POST

/api/v1/sdk/purchase/stripe/token/validate/

Validate Stripe purchase

POST

/api/v2/server-side-api/profile/

Create profile

GET

/api/v2/server-side-api/profile/

Get profile

PATCH

/api/v2/server-side-api/profile/

Update profile

DELETE

/api/v2/server-side-api/profile/

Delete profile

POST

/api/v2/server-side-api/purchase/profile/grant/access-level/

Grant access level

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Adapty secret API key is stored encrypted in the Jentic MAXsystem vault and injected into the Authorization header at execute time. Agents never receive the raw secret in their context.

Intent-based discovery

Agents search by intent (e.g., 'grant access level to user') and Jentic returns the matching Adapty operation with its input schema — critical because Adapty does not publish a public OpenAPI spec.

Time to first call

Direct integration without a published spec: 1-2 days reverse-engineering request shapes from the docs site. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Stripe API

Handles the actual web payment that Adapty's Stripe validation endpoint then attaches to a profile.

Use Stripe to charge the card, then call Adapty's Stripe validate endpoint to grant the user access on mobile.

Alternative

Recurly API

Subscription billing platform with its own entitlement model, not mobile-native.

Choose Recurly when the product is web-first or B2B SaaS rather than a mobile app with App Store/Play Store IAP.

Alternative

Paddle API

Merchant-of-record subscription platform covering checkout, tax, and entitlements end-to-end.

Pick Paddle when you want a single platform handling checkout and tax compliance, not a mobile-IAP-plus-web stitching layer.

FAQs

Specific to using Adapty server-side API API through Jentic.

Why is there no official OpenAPI spec for Adapty server-side API?

Adapty does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Adapty server-side API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Adapty server-side API use?

The API uses an API-key scheme: a secret key is sent in the Authorization header on every request. In Jentic the secret key is stored encrypted in the MAXsystem vault and injected at execute time so it never leaves the vault into agent context.

Can I grant or revoke entitlements with the Adapty server-side API?

Yes. POST /api/v2/server-side-api/purchase/profile/grant/access-level/ adds an access level to a profile, and POST /api/v2/server-side-api/purchase/profile/revoke/access-level/ removes it. Both accept a customer_user_id and an access_level_id and are typically used for support concessions or chargeback handling.

How do I sync a Stripe web purchase to an Adapty profile through Jentic?

Search Jentic for 'validate stripe purchase adapty', load the POST /api/v1/sdk/purchase/stripe/token/validate/ schema, and execute with the Stripe token and customer_user_id. The subscription becomes visible to the mobile SDK on the next profile fetch.

Are there rate limits on the Adapty server-side API?

Adapty enforces per-account rate limits scaled to the subscription tier; details are not declared in the spec. When the limit is hit Jentic surfaces the 429 response with Adapty's Retry-After header so a backoff strategy can be applied.

Does this API replace the Adapty mobile SDK?

No. The server-side API complements the mobile SDK — the SDK handles in-app purchase flows on iOS and Android, while the server-side API is for backend reconciliation, support-driven entitlement changes, and web purchase validation.