Appcharge
Appcharge is a monetization and payments platform (merchant of record) for mobile game publishers. It lets studios sell in-game offers direct-to-consumer outside the app stores through a hosted web store, a mobile Checkout SDK, and Payment Links — covering checkout sessions, price localization, coupons and promo codes, refunds, web-store offers (bundles, daily bonuses, rolling/special offers, progress bars, reward calendars, triggered popups), offer components, game-portal content, media assets, translations, financial and analytics reporting, and player personalization/authentication callbacks. The REST API authenticates with an x-publisher-token API-key header; webhooks and Appcharge-to-publisher callbacks are HMAC-SHA256 signed with a replay window; and a hosted MCP server exposes agent access over OAuth 2.0 (authorization_code + PKCE).
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Appcharge the way a machine reads it — 43 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Appcharge scores 65.6/100 (strong), with a separate agent-readiness read of 61/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Put this on your own site. The badge is drawn live from Appcharge's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/appcharge/"
title="Appcharge on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/appcharge.svg"
alt="Appcharge Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/appcharge/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/appcharge/"
title="Appcharge on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/appcharge/card.svg"
alt="Appcharge Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Appcharge
Each block below is one kind of artifact we hold for Appcharge. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Appcharge Assets API
The Assets API from Appcharge — 2 operation(s) for assets.
Appcharge Authentication API
The Authentication API from Appcharge — 2 operation(s) for authentication.
Appcharge Badges API
The Badges API from Appcharge — 2 operation(s) for badges.
Appcharge Coupons API
The Coupons API from Appcharge — 2 operation(s) for coupons.
Appcharge General API
The General API from Appcharge — 9 operation(s) for general.
Appcharge Localization API
The Localization API from Appcharge — 1 operation(s) for localization.
Appcharge Offer Designs API
The Offer Designs API from Appcharge — 2 operation(s) for offer designs.
Appcharge Offers API
The Offers API from Appcharge — 5 operation(s) for offers.
Appcharge Orders API
The Orders API from Appcharge — 1 operation(s) for orders.
Appcharge Personalization API
The Personalization API from Appcharge — 1 operation(s) for personalization.
Appcharge Popups API
The Popups API from Appcharge — 1 operation(s) for popups.
Appcharge Portal Content API
The Portal Content API from Appcharge — 4 operation(s) for portal content.
Appcharge Products API
The Products API from Appcharge — 2 operation(s) for products.
Appcharge Promo Codes API
The Promo Codes API from Appcharge — 3 operation(s) for promo codes.
Appcharge Rolling Offers API
The Rolling Offers API from Appcharge — 2 operation(s) for rolling offers.
Appcharge Store Refresh Popups API
The Store Refresh Popups API from Appcharge — 2 operation(s) for store refresh popups.
Appcharge Triggered Popups API
The Triggered Popups API from Appcharge — 2 operation(s) for triggered popups.
Scroll within the panel for all 17 ·
Postman Collections 17
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Appcharge Assets API
POSTMANAppcharge Assets Badges API
POSTMANAppcharge Assets Coupons API
POSTMANAppcharge Assets General API
POSTMANAppcharge Assets Offers API
POSTMANAppcharge Assets Orders API
POSTMANAppcharge Assets Popups API
POSTMANScroll within the panel for all 17 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
appcharge-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Appcharge Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Appcharge Events (V2) Webhooks
Appcharge sends real-time, structured webhook events (Events V2) to a publisher-registered HTTPS endpoint for order lifecycle, web store and game portal interactions, logins, an...
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Appcharge — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 5
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/appcharge · machine-readable index on apis.io
This is an independent, third-party profile of Appcharge, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
[email protected]
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.