ironSource
ironSource is a Tel Aviv-based mobile game growth platform, acquired by Unity Technologies in a $4.4B all-stock deal that closed in November 2022 and is now operated as part of Unity's Grow Solutions group. The company builds an end-to-end suite for mobile game developers spanning ad monetization, user acquisition, and ad operations. Its flagship product LevelPlay is a unified in-app bidding and ad mediation platform that brokers Rewarded Video, Interstitial, and Banner ad demand across the ironSource Ads network, AdMob, AppLovin, Meta Audience Network, Pangle, Mintegral, Unity Ads, Vungle, and dozens of other ad sources. ironSource Ads is its self-serve ad network and user-acquisition platform offering CPI, CPE, ROAS-optimized, and SKAdNetwork-aware campaign management. Adjacent products include Aura (an on-device content marketplace for carriers and OEMs that originated from the 2021 Bigabid/Soomla portfolio and earlier hardware OEM deals), Tapjoy Offerwall (acquired 2022) for rewarded engagement, and Ad Quality for ad-content monitoring. Developer access is via a REST surface hosted at platform.ironsrc.com — including the Monetization Reporting API (v5/v4), ironSource Ads Reporting API, Application API (v6), Campaign API suite (Campaigns, Audiences, Country Groups, Bidding, Assets, Creatives), SKAN Reporting API, and Cost API — authenticated with Bearer tokens issued from the platform dashboard. Real client integration is delivered via native SDKs (iOS, Android, Unity, Flutter, React Native, Adobe AIR, Xamarin) plus the LevelPlay mediation adapter ecosystem published on github.com/ironsource-mobile. As of 2026 the developers.is.com knowledge center 301-redirects to docs.unity.com, consolidating ironSource documentation inside Unity Grow alongside Unity Ads. No public OpenAPI, Postman collection, or JSON Schema bundle is published by ironSource for the REST surface; documentation is human-readable HTML on docs.unity.com/en-us/grow.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles ironSource the way a machine reads it — 1 machine-readable artifact, 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 — ironSource scores 13.9/100 (minimal), with a separate agent-readiness read of 10/100 (human only). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile ironSource
Each block below is one kind of artifact we hold for ironSource. 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.
Security Posture 1
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.
Resources
Every other property we hold for ironSource — 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.
Documentation 1
Reference material describing how the API behaves
Build 8
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 8 ·
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 13
Properties that don't map to a standard resource type
Scroll within the panel for all 13 ·
← All providers · Data indexed from github.com/api-evangelist/ironsource · machine-readable index on apis.io