API reference
API reference
Two APIs: serve handles ad requests in your app. The control API manages apps, campaigns, and billing in the console.
Base URLs
| Use case | Host |
|---|---|
| Request ads, impressions, and clicks | https://serve.meridianads.tech |
| Manage apps, campaigns, and billing | https://api.meridianads.tech |
| AI agent tools (MCP) | https://mcp.meridianads.tech |
| Console and these docs | https://meridianads.tech |
Download the full spec as api/openapi.yaml from the Meridian Ads GitLab repo, or fetch /openapi.yaml from this site.
Serve API
integrate hereMost publishers only need these three endpoints. Authenticate with HMAC using your SDK key. See Authentication for signing details.
| Method | Path | Auth | What it does |
|---|---|---|---|
| POST | /v1/decision | HMAC | Request an ad. Returns 200 with a creative, or 204 when nothing matches. |
| POST | /v1/events | HMAC | Record an impression after the creative is visible. |
| GET | /v1/click/{token} | Token | Track a click and redirect to the advertiser landing URL. |