Introduction
Adelion API Docs
Section titled “Adelion API Docs”Welcome to the Adelion API documentation.
The Adelion API is a REST API for managing platform resources such as publishers, advertisers, VAST tags, RTB endpoints, pop feeds, and DSP integrations. These docs describe each endpoint, required parameters, request examples, response formats, and possible error codes.
Getting started
Section titled “Getting started”To use the API, first authenticate with your Adelion username and password. A successful login returns an AccessToken, which must be included in the Authorization header for API requests that require authorization.
Authorization: Bearer [AccessToken]Content-Type: application/jsonBase URL
Section titled “Base URL”https://adelion.com/apiAPI sections
Section titled “API sections”| Section | Description |
|---|---|
| Auth | Log in, log out, refresh tokens, and retrieve account information. |
| Publisher | Create, update, activate, deactivate, and retrieve publishers. |
| VAST Tag | Manage publisher VAST tag integrations. |
| RTB EP | Manage publisher RTB endpoints. |
| Pop Feed | Manage publisher pop feed integrations. |
| Advertiser | Create, update, activate, deactivate, and retrieve advertisers. |
| DSP RTB EP | Manage DSP RTB endpoints. |
| DSP VAST Tag | Manage DSP VAST tag integrations. |
| DSP Pop Feed | Manage DSP pop feed integrations. |
Request format
Section titled “Request format”Most API endpoints accept JSON request bodies.
{ "ExampleField": "Example value"}Use the following headers when sending JSON requests:
| Header | Value | Required | Description |
|---|---|---|---|
Authorization | Bearer [AccessToken] | Yes | Access token returned by the login endpoint. |
Content-Type | application/json | Yes | Indicates that the request body is JSON. |
Response format
Section titled “Response format”Most endpoints return JSON responses.
Successful requests return the requested data and an HTTP status code such as 200.
{ "Status": "Ok"}Failed requests return an error response with a status message and error description.
{ "Status": "Error", "Error": "[error description]"}Status codes
Section titled “Status codes”| Code | Status | Meaning |
|---|---|---|
200 | OK | The request completed successfully. |
400 | Bad Request | The request body is not valid JSON or the request is malformed. |
401 | Unauthorized | The access token is missing or invalid. |
406 | Not Acceptable | One or more required values are missing or malformed, or the requested object was not found. |
500 | Internal Server Error | The server encountered a problem. Try again later. |
Next steps
Section titled “Next steps”Start with the Auth section to get an access token. Then continue to the API section you want to use.