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.

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.