Vungle website screenshot

Vungle

Vungle is a mobile app monetization and user-acquisition platform, now operated as part of Liftoff (the merged Liftoff + Vungle mobile growth company). Vungle's in-app advertising SDKs help mobile publishers monetize with performance-focused ad formats (video, interactive, and playable ads), while Liftoff's advertiser APIs let growth teams launch and manage user-acquisition campaigns, assemble creatives, ingest audiences, and pull automated performance reporting. The programmatic surface is documented at docs.liftoff.io and includes a Reporting API, a closed-beta Campaign Management API, an Audiences Integration API, a GDPR Opt-Out API, and a server-to-server (S2S) postback integration. All advertiser APIs authenticate with an HTTP Basic API key and secret issued by a Liftoff Account Manager.

Vungle publishes 4 APIs on the APIs.io network. Tagged areas include Company, Advertising, Mobile, Monetization, and User Acquisition.

The Vungle catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Vungle’s developer surface includes documentation, getting-started guide, authentication, sandbox, engineering blog, and 17 more developer resources.

39.7/100 developing ▬ flat Agent 25/100 agent aware Front door AI 4/6 moderate saas Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0
4 APIs
CompanyAdvertisingMobileMonetizationUser AcquisitionAdTechAnalyticsReporting

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/vungle: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Liftoff Reporting API

Automated access to Vungle/Liftoff campaign performance reports — impressions, clicks, installs, and in-app events — with configurable groupings, metrics, and cohort (look-back ...

Liftoff Campaign Management API

Closed-beta API to programmatically launch UA expansion campaigns, manage spend and targeting, upload assets, and assemble creatives. Standard REST/JSON at https://cm-api.liftof...

Liftoff Audiences Integration API

Audience ingestion/validation API for partners working on behalf of multiple clients, at https://analytics.liftoff.io/audiences/v1.

Liftoff GDPR Opt-Out API

Submit GDPR-compliant opt-out requests to remove user data by device ID, at https://analytics.liftoff.io/opt_out/v3.

Rate Limits 1

Documented rate limits and quota policies.

Vungle Rate Limits

1 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Vungle Authentication

http · 1 scheme

SECURITY

Vungle Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

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

Source (apis.yml)

apis.yml Raw ↑
aid: vungle
name: Vungle
description: Vungle is a mobile app monetization and user-acquisition platform, now operated as part of Liftoff (the merged
  Liftoff + Vungle mobile growth company). Vungle's in-app advertising SDKs help mobile publishers monetize with performance-focused
  ad formats (video, interactive, and playable ads), while Liftoff's advertiser APIs let growth teams launch and manage user-acquisition
  campaigns, assemble creatives, ingest audiences, and pull automated performance reporting. The programmatic surface is documented
  at docs.liftoff.io and includes a Reporting API, a closed-beta Campaign Management API, an Audiences Integration API, a
  GDPR Opt-Out API, and a server-to-server (S2S) postback integration. All advertiser APIs authenticate with an HTTP Basic
  API key and secret issued by a Liftoff Account Manager.
url: https://raw.githubusercontent.com/api-evangelist/vungle/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
- gv
- uncork-capital
x-tier: stub
x-tier-reason: portfolio-lead
x-operated-by: Liftoff
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 14
  pass: local-v1
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  - sandbox
  - url: https://vungle.com
    status: 301
    note: declared website redirects to https://liftoff.ai/ — a different registrable domain (vungle.com -> liftoff.ai), possible
      rename or acquisition (probed 2026-09-03, roadmap#169)
  generated: '2026-09-03'
  method: derived
image: https://liftoff.ai/wp-content/uploads/2025/01/B-Meta-Image-20240912-122239.jpg
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Advertising
- Mobile
- Monetization
- User Acquisition
- AdTech
- Analytics
- Reporting
tags_raw:
- Company
- Advertising
- Mobile
- Monetization
- User Acquisition
- Ad Tech
- Analytics
- Reporting
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Liftoff Reporting API
  description: Automated access to Vungle/Liftoff campaign performance reports — impressions, clicks, installs, and in-app
    events — with configurable groupings, metrics, and cohort (look-back window) analysis. HTTP Basic authenticated; JSON.
  humanURL: https://docs.liftoff.io/advertiser/reporting_api
  baseURL: https://data.liftoff.io/api/v1
  properties:
  - type: Documentation
    url: https://docs.liftoff.io/advertiser/reporting_api
  - type: Authentication
    url: authentication/vungle-authentication.yml
- name: Liftoff Campaign Management API
  description: Closed-beta API to programmatically launch UA expansion campaigns, manage spend and targeting, upload assets,
    and assemble creatives. Standard REST/JSON at https://cm-api.liftoff.io/v1.
  humanURL: https://docs.liftoff.io/advertiser/campaign_management_api
  baseURL: https://cm-api.liftoff.io/v1
  properties:
  - type: Documentation
    url: https://docs.liftoff.io/advertiser/campaign_management_api
- name: Liftoff Audiences Integration API
  description: Audience ingestion/validation API for partners working on behalf of multiple clients, at https://analytics.liftoff.io/audiences/v1.
  humanURL: https://docs.liftoff.io/advertiser/direct/liftoff-api-audiences
  baseURL: https://analytics.liftoff.io/audiences/v1
  properties:
  - type: Documentation
    url: https://docs.liftoff.io/advertiser/direct/liftoff-api-audiences
- name: Liftoff GDPR Opt-Out API
  description: Submit GDPR-compliant opt-out requests to remove user data by device ID, at https://analytics.liftoff.io/opt_out/v3.
  humanURL: https://docs.liftoff.io/advertiser/direct/liftoff-gdpr-opt-out-api
  baseURL: https://analytics.liftoff.io/opt_out/v3
  properties:
  - type: Documentation
    url: https://docs.liftoff.io/advertiser/direct/liftoff-gdpr-opt-out-api
common:
- type: DomainSecurity
  url: security/vungle-domain-security.yml
- type: Website
  url: https://vungle.com
- type: DeveloperPortal
  url: https://docs.liftoff.io/
- type: Documentation
  url: https://docs.liftoff.io/
- type: GettingStarted
  url: https://docs.liftoff.io/advertiser
- type: Authentication
  url: authentication/vungle-authentication.yml
- type: Conventions
  url: conventions/vungle-conventions.yml
- type: ErrorCatalog
  url: errors/vungle-error-codes.yml
- type: RateLimits
  url: rate-limits/vungle-rate-limits.yml
- type: Lifecycle
  url: lifecycle/vungle-lifecycle.yml
- type: Sandbox
  url: sandbox/vungle-sandbox.yml
- type: Packages
  url: packages/vungle-packages.yml
- type: SDKs
  url: packages/vungle-packages.yml
- type: X-MCPServerCandidate
  url: mcp/vungle-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/vungle-llms.txt
- type: Conformance
  url: conformance/vungle-conformance.yml
- type: DataModel
  url: data-model/vungle-data-model.yml
- type: Webhooks
  url: asyncapi/vungle-s2s-webhooks.yml
- type: Blog
  url: https://liftoff.io/blog
- type: PrivacyPolicy
  url: https://liftoff.io/privacy-policy
- type: TermsOfService
  url: https://liftoff.io/terms-of-service
- type: GitHubOrganization
  url: https://github.com/Vungle

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/vungle"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/vungle/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/vungle/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.