Integrating Outbrain API into Anti-Gravity for ease of launch +optimisation

[Paul Gray]

Hey there,

I need help with this:

The dashboard cookie tokens (OB-TOKEN-V1) are read-only — confirmed with both your token and the Amesmo token. The API docs at

amplifyv01.docs.apiary.iodescribe a different auth flow:API credentials — a dedicated username + password for API access (NOT the dashboard login)

You authenticate at: GET /amplify/v0.1/login with Authorization: Basic {base64(username:password)}

1. 1. That returns a write-enabled API token

Can you ask the reps: "Can you enable Amplify API write access for our account ) and provide us with API credentials (username + password) for the /login endpoint?"

I am still hitting a 405 Method Not Allowed error when trying to create campaigns via the Outbrain API. This confirms that the current session token (V1) is read-only.

I need one of the following to proceed with the Outbrain setup (C6–C11):

1. Outbrain API Credentials: Username and Password for the Amplify API (different from the dashboard login).
2. Account Representative: Ask your Outbrain rep to enable "API Write Access" or provide an API secret.

Alternatively, I can wait for the credentials while you review the Taboola setup in walkthrough.md

My account is under this email - paulgr...@gmail.com. 

Many thanks

Paul 

[kaja.gros]

Hi Paul,

Thank you for reaching out to Amplify API Support.

We’ve confirmed that the email address paulgr...@gmail.com has access to the Amplify API. Please also check your role on the advertiser where you’re trying to create campaigns. Owners and Admins can create new campaigns; Viewers cannot.

If your role is Admin or Owner, the token generated either via the web interface or via the API using the endpoint (GET) https://api.outbrain.com/amplify/v0.1/login is valid for creating new campaigns.

Could you let me know which method and endpoint you’re using to create campaigns, and share the request body? Note that to create campaigns via the API, you first need to create a budget under the marketer and then use that budget ID when creating the campaign via (POST) https://api.outbrain.com/amplify/v0.1/campaigns which you can see explained here.

If, after these steps, you’re still seeing the same error, please share:

• The advertiser ID for the advertiser where you’re trying to create campaigns
• The exact endpoints and methods you’re calling
• The request body and the full error response (if available)

Best regards,
Kaja

[Paul Gray]

Hey,

yes admin, budget being created. then just get  405 Method Not Allowed errors. 

FYI, this doesnt open to anything - https://amplifyv01.docs.apiary.io/#reference/campaigns/campaigns/create-a-new-campaign

1. Advertiser (Marketer) ID

00e8330cbc2c581919bc2f1cc1019b75e5

2. Endpoints and Methods

I have been testing campaign creation via the standard Amplify v0.1 endpoints:

• Marketer-Specific Endpoint: POST https://api.outbrain.com/amplify/v0.1/marketers/00e8330cbc2c581919bc2f1cc1019b75e5/campaigns
• Global Endpoint: POST https://api.outbrain.com/amplify/v0.1/campaigns

3. Request Body and Error Response

Request Body (Minimal Example):

json

{

"name": "OB-9 Scotland NE Sniper",

"enabled": false,

"cpc": 0.55,

"budgetId": "00e01b763ffe283bd0115cf8ee437eebba",

"onAirType": "StartImmediately"

}

Error Response:

• Status Code: 405 Method Not Allowed
• Response Body:

json

{

"timestamp": 1771930675145,

"status": 405,

"error": "Method Not Allowed",

"requestId": "663e109b-1292319"

}

[kaja.gros]

Hi Paul,

Regarding the URL not opening: the API documentation was briefly unavailable yesterday, but it should be accessible today.

For the endpoint, please use the global one:
POST https://api.outbrain.com/amplify/v0.1/campaigns

About the request body: although your example was minimal, a few mandatory fields were missing. In addition to what you included, you need:

• targeting
• objective (campaign objective)

Also, the value StartImmediately is not valid for onAirType. Please either remove onAirType or set it to Scheduled or StartHour.

A minimal valid example would look like:

{
"name": "OB-9 Scotland NE Sniper",
"enabled": false,
"cpc": 0.55,
"budgetId": "00e01b763ffe283bd0115cf8ee437eebba",

"targeting": {
"platform": ["DESKTOP", "MOBILE"],
"operatingSystems": ["MacOs", "Windows"],
"browsers": ["Chrome"],
"language": "en"
},
"objective": "Traffic"
}

If it still doesn’t work, please share the full request body (not just the minimal example), and we’ll take a closer look.

Best regards,

Kaja