Adapty server-side API

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

★ Only Publicly Available OpenAPI DocumentPaymentsBilling 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.

Install Jentic One Beta

Connect the Adapty server-side API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adapty server-side API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Adapty server-side 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

GET STARTED

Start building with Adapty server-side API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Adapty server-side 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 your Jentic One instance 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 Jentic?

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

Credential isolation

Your Adapty secret API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'grant access level to user', and Jentic returns the matching Adapty operation with its input schema so the agent calls the right endpoint without browsing the reference docs, which matters because Adapty does not publish a public OpenAPI spec.

Time to first call

FAQs

Specific to using Adapty server-side 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 with Jentic One, the self-hosted execution layer.

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the Adapty server-side API?

Yes. Because you run Jentic One yourself, your own rules decide which Adapty operations and credentials the agent can use, and these endpoints pass the profile and access-level details in the query or request body rather than a resource id in the URL. You can scope the agent to only the operations it needs, such as reading a profile with GET /api/v2/server-side-api/profile/ or granting an access level with POST /api/v2/server-side-api/purchase/profile/grant/access-level/. Higher-impact calls like revoking an access level or deleting a profile stay off limits unless you explicitly add them. Your secret API key is stored by your own instance and injected at execution time, so it never enters the agent's context.

Adapty server-side API

Connect the Adapty server-side API to your agent

Capabilities

Start building with Adapty server-side API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs