Unable to authenticate after password reset

[Thomas Jaehnigen]

Starting with us trying to pull data from the Reporting API on May 31st (to look at May 30 data), we started getting this error message -

Unauthorized: Authentication token was either missing or invalid After reading some of the comments here, we reset the password. We tried again, and it still failed, this time stating simply 'authentication failed'.

So this morning, we reset the password again, and it continues to return 'authentication failed'.

We took a look at the Outbrain Reporting API. It looks like we are still using v1 of the Outbrain Reporting API. We see there is a different version, Outbrain Reporting API v2 - should we upgrade to this new version? When was Outbrain Reporting API v1 deprecated? When was a notification sent out that it was being deprecated (if it is deprecated)?

Is there a documentation link that explains where we can generate a new token? The reset password itself works, we need the new token for our data flows.

We urgently need resolution to this issue.

The account where we reset the password is marc.g...@digitalturbine.com (we reset it twice, once on Monday and once again today Tuesday June 3, 2025).

[nadav.porat]

hey, 
v1 is not deprecated yet. 
pls try after resetting the password to create a new token 
we can zoom if it is still not working. (send me an invite nadav...@teads.com)

Nadav

[Thomas Jaehnigen]

Thanks for the reply.

We programmatically ask for a refreshed token every time we call to the API.  We have not changed any of our code in a long time. It's been running fine for years.

Here is the Outbrain Engage documentation we are referring to -- 
---This --> https://outbrainapioverview.docs.apiary.io/#introduction/apis-for-publishers 
---And This --> https://engagereportsapioutbrainv21.docs.apiary.io/#reference/overview-and-entities/authentication

We do not want to have to manually create a new token every so many days (not sure when you guys expire the token) as we just want to refresh the token every day if needed.

Here is a code snippet that is relevant - 

username_password = f"{username}:{password}" print(f'username password: {username_password}') username_password_bytes = username_password.encode("ascii") base64_bytes = base64.b64encode(username_password_bytes) base64_message = base64_bytes.decode("ascii") headers = {"Authorization": f"Basic {base64_message}"} response = requests.get("https://api.outbrain.com/engage/v2/login", headers=headers) print('url: https://api.outbrain.com/engage/v2/login') response_text = json.loads(response.text) print(f'response text: {response_text}') token = response_text["OB-TOKEN-V1"]

Before we get on a Zoom (we can send a link) can you please review that we are doing this all correctly? Again, we have not changed code in a long time, it's been running fine for years.

I await your reply.

[nadav.porat]

Your code looks ok,
Are you sure you are using the new password? 

Nadav

[Thomas Jaehnigen]

FYI - the issue is that, when we try to obtain/acquire/refresh the token, if fails - We are explicitly following the Outbrain documentation.

It may be easier to do this on a Zoom call. I can set up a date/time if I know your availability. We are USA eastern time zone (UTC -4).

Please advise!

--
You received this message because you are subscribed to the Google Groups "EngageApi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to engageapi+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/engageapi/9dc59b65-c5cf-4be2-ba3a-05686a6868f8n%40googlegroups.com.

--

Thomas Jaehnigen CM Business Operations Lead www.digitalturbine.com

IMPORTANT: The content of this email message and any attachments may contain confidential information intended solely for the recipient(s) listed. If you received this email in error, please notify the sender, delete it immediately, and do not disclose its content to anyone or make copies thereof.