Skip to content

Gateway API Documentation

The Gateway API is Arago DSP’s core management surface for the full DSP console. It provides a complete set of endpoints covering campaign lifecycle, line items, creatives, targeting, reporting, and more. Everything needed to build and operate the platform.

Full Platform Surface

Exposes the complete DSP feature set—campaigns, line items, creatives, targeting, reporting, and administration—beyond the campaign-focused Portal.

User & Role Scoped

JWT Bearer authentication with fine-grained permissions, so each operator sees only the capabilities their role grants.

Internal Operators

Built for DSP operators and internal tooling, using login credentials (username/password with optional MFA), unlike the Portal’s partner API keys.

Comprehensive Reference

Full interactive OpenAPI reference generated from live protobuf definitions, covering the entire gateway surface.

The Arago DSP platform uses JWT Bearer Authentication mechanism.

Access tokens are obtained by authenticating via public login endpoint and are required for all subsequent API requests to the gateway.

Login to the Arago DSP platform via the public login endpoint:

Login request
curl -X POST https://public-gateway.staging.arago-tech.com/auth/login \
-H "Content-Type: application/json" \
-d '{
"email": "replace_with_your_email",
"password": "replace_with_actual_password"
}'

The response will contain a JSON object with the access_token, refresh_token, and MFA information (if applicable):

Response
{
"access_token": "<ACCESS_TOKEN>",
"refresh_token": "<REFRESH_TOKEN>"
}

For all subsequent API requests to the Gateway API endpoints, include the access_token in the Authorization header as a Bearer token:

List campaigns
curl -X GET https://gateway.staging.arago-tech.com/line-items/campaigns \
-H "Authorization: Bearer <ACCESS_TOKEN>"

An example response for a successful request:

Response
{
"campaigns":[
{
"id":"63e2d42a27ad5f2b345ca124",
"name":"My first campaign",
"description":"none",
"created_at":"2026-01-01T14:00:00Z",
"updated_at":"2026-01-31T15:00:00Z",
"start_date":"2026-01-15T08:00:00Z",
"end_date":"2026-01-31T23:59:59Z",
"line_item_count":8,
"status":"STATUS_PLAYING",
}
],
"full_text_search":true,
}

Logout via the gateway logout endpoint to revoke both the access token and the refresh token. The request must include the access_token in the Authorization header and the refresh_token in the JSON body:

Logout request
curl -X POST https://gateway.staging.arago-tech.com/auth/logout \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-d '{
"refresh_token": "xxx"
}'

On success the endpoint returns an empty JSON object:

Response
{}