Teads AmplifyAPI Integration

[Ellie Stockwell]

Hi,

Our team is trying to integrate the Outbrain AmpligyAPI connection, but we are getting this error when trying to connect: 

Failed to connect to API

Server is not responding with correct response after specific retries and giving status code [401] and status message [No valid token found]

What do we need to do to get this resolved, or make sure it works? Our team is using FiveTran, we saw an Outbrain connector, but it cannot use an API key.

Let me know!

Thanks!

[Bryn Whitcomb]

Hey Ellie, 

Thanks for reaching out!

We do require a valid authentication token to be sent in each API request. You can generate a token via an API call or via the Amplify dashboard. More details on how to do that here: https://amplifyv01.docs.apiary.io/#reference/authentications/retrieve-a-single-marketer

I'm not familiar with FiveTran's API connector specifically, but all you should need to do is provide the token you generated in the header of your API calls in this format: "OB-TOKEN-V1: MY_ACCESS_TOKEN"

Please let us know if you need further assistance with this!

Best, 

Bryn

On Wed, Feb 4, 2026 at 1:21 PM Ellie Stockwell <estoc...@theshipyard.com> wrote:

Teads finds this email suspicious! The sender estockwell @ theshipyard.com may look familiar to you, but this email might be an impersonation attempt

--
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/bfe7e1c8-daa1-4207-aa57-90a4864b153bn%40googlegroups.com.

--

Bryn Whitcomb Senior Technical Solutions Engineer e | bryn.w...@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.