Request for Amplify API Access Activation

[Julian BATARD]

Hello Outbrain Support Team,

I am currently developing a local MCP server to interact with the Outbrain Amplify API.

However, I am facing an authentication issue. My Python script is targeting the https://api.outbrain.com/amplify/v0.1/login endpoint to generate a dynamic token using my standard account credentials. While these credentials work perfectly to log into the Outbrain dashboard, the API rejects them.

Could you please review my account and enable the necessary API permissions ?

Here are my details:

• User Email:  same email address I use

• Marketer ID: 00960bbe962f73ece8f1c3138267e79bbc

Thank you in advance for your help!

Best regards,

Julian

[Marta Bernasconi]

Hi Julian,

Thank you for reaching out!

Your user has API access. 

To better assist you, could you please provide the following information:

- the whole HTTP request structure that you are sending (does it include a header named Authorization value: BASIC BASE-64-ENC(YOUR_OUTBRAIN_USER_NAME:YOUR_OUTBRAIN_PASSWORD)?)

- the exact error you get.

Thank you,

Best,

On Wed, Apr 29, 2026 at 3:29 PM Julian BATARD <jba...@prismamedia.com> wrote:

Teads couldn't recognize this email as this is the first time you received an email from this sender jbatard @ prismamedia.com

--
You received this message because you are subscribed to the Google Groups "Outbrain-AmplifyApi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to outbrain-amplif...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/outbrain-amplifyapi/f78878f9-a51c-4f38-8ce8-6876bbc681ccn%40googlegroups.com.

--

Marta Bernasconi Senior Technical Solutions Engineer e | marta.be...@teads.com

The information in this email is confidential and intended only for the addressee(s) named above. If you are not the intended recipient, any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. Teads does not warrant that any attachment(s) are free from viruses or other defects and accepts no liability for any losses resulting from infected email transmission. Please note that any views expressed in this email may be those of the originator and do not necessarily reflect those of the organization. For more information or feedback, contact us here.