InMobi

InMobi Server-to-Server Ad Request API

Lets a publisher request InMobi ads from its own servers rather than through the client SDK, using the InMobi ad-request/ad-response contract at /showad/v3.1. The caller is identified by an InMobi Property ID carried in the request payload rather than by an authentication header. Verified live 2026-08-12.

GitHub

Documentation

📖
Documentation
https://support.inmobi.com/monetize/integration/monetization-server-to-server-api-integration-guides/api-3.1-server-to-server-integration-guidelines

Other Resources

🔗
SourceCode
https://github.com/InMobi/api-monetization

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/inmobi-server-to-server-ad-request-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

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.

GitHub Google LinkedIn

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

API entry from apis.yml

apis.yml Raw ↑ 
aid: inmobi:inmobi-server-to-server-ad-request-api
name: InMobi Server-to-Server Ad Request API
description: Lets a publisher request InMobi ads from its own servers rather than through the client SDK,
  using the InMobi ad-request/ad-response contract at /showad/v3.1. The caller is identified by an InMobi
  Property ID carried in the request payload rather than by an authentication header. Verified live 2026-08-12.
humanURL: https://support.inmobi.com/monetize/integration/monetization-server-to-server-api-integration-guides/api-3.1-server-to-server-integration-guidelines
baseURL: https://api.w.inmobi.com
tags:
- Ad Serving
- Monetization
properties:
- type: Documentation
  url: https://support.inmobi.com/monetize/integration/monetization-server-to-server-api-integration-guides/api-3.1-server-to-server-integration-guidelines
- type: SourceCode
  url: https://github.com/InMobi/api-monetization
x-evidence:
  verified: '2026-08-12'
  method: live GET and POST
  url: https://api.w.inmobi.com/showad/v3.1
  http_status: 204
  note: Live routed ad-serving host; an empty request returns 204 No Content (no ad), which is correct
    behaviour rather than an error. The linked SourceCode repo is InMobi's own seven-language client for
    the prior "API 2.0" generation of this endpoint and has not been updated since 2016.