Regarding data not received

[Akari Tonda]

Hi team,

I am writing to request an investigation regarding an issue our client is experiencing with your API.

Despite updating their authentication tokens, our client has been unable to retrieve data since August 9 (JST). Whenever they make a request, the following 401 error is returned:

> 401: Authentication token was either missing or invalid

> Client’s account address: a...@mirai-kirei.jp

Could you please investigate the cause of this error and advise us on how to resolve the issue?
If you need any log data or additional details, please let us know.

Since I have also received inquiries from other accounts regarding the same issue, we would greatly appreciate it if you could investigate this as soon as possible.

Regards,

Akari

[Bryn Whitcomb]

Hey Akari, 

Thanks for reaching out! 

Could you please share the exact endpoint this user is trying to call? Please be sure to include any specific IDs and parameters. 

Best, 

Bryn

--
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/b855ac00-7956-4261-ac33-07bcad98d40dn%40googlegroups.com.

--

Bryn Whitcomb Team Lead, Technical Solutions Engineering 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.

[Akari Tonda]

Hi Bryn,

I am sharing the details of the client's Outbrain Amplify API setup and call patterns for your review.

1. Executed Endpoints (GET Only)

• Base URL: [https://api.outbrain.com/amplify/v0.1](https://api.outbrain.com/amplify/v0.1)

• Marketer ID: 0001c8c3bc46fe4e2fabd4e864a05e7d8f (JP_Vitabrid_ActiveRich5)

• Daily Batch (Every Morning):

  • GET /marketers/{marketerId}/campaigns

  • GET /reports/marketers/{marketerId}/campaigns/periodic

  • GET /reports/marketers/{marketerId}/promotedContent

• Weekly & Monthly (Mondays and 1st of every month):

  • GET /reports/marketers/{marketerId}/sections

• Connectivity Test Only (Manual):

  • GET /marketers

Note: We have not implemented any POST, PUT, or DELETE requests. We also do not use the /login endpoint; instead, we re-use a token generated directly from the management console.

2. Request Parameters

• Campaign List (/campaigns):

  • limit=50, offset=0, 50, ... (paginated until totalCount is reached).

• Campaign Periodic Performance (/campaigns/periodic):

  • from = 8 days ago, to = yesterday, breakdown=daily, limit=500, includeConversionDetails=true.

• Promoted Content Performance (/promotedContent):

  • limit=50, offset (increments of 50), sort=-spend, includeConversionDetails=true.

  • Fetched for both the last 7 days and daily units (from=to) for the last 3 days (as breakdown=daily is unavailable for this endpoint).

• Section Performance (/sections):

  • limit=100, offset (increments of 100), sort=-spend, includeConversionDetails=true.

  • Fetched for the previous week (7 days) on Mondays, and the previous month on the 1st of each month.

Note: All dates are formatted as yyyy-MM-dd in JST. We retrieve metrics in bulk using Marketer-level report endpoints rather than specifying individual Campaign IDs.

3. Request Headers (Curl Example)
Only the authorization header is sent:

curl -H "OB-TOKEN-V1: ***REDACTED***" \
  "https://api.outbrain.com/amplify/v0.1/reports/marketers/0001c8c3bc46fe4e2fabd4e864a05e7d8f/campaigns/periodic?from=2026-08-13&to=2026-08-20&breakdown=daily&limit=500&includeConversionDetails=true"

  Note: Tokens are securely stored in script properties and are never printed in code, logs, or spreadsheets.  

※ Rate Limits & Error Handling

＊To respect the rate limit of 10 requests/minute/marketer for performance report APIs, we insert a delay of at least 6.5 seconds between requests for /reports endpoints.

＊Factoring in response latency, the actual interval is around 7–9 seconds (~6–8 requests per minute).

＊A single batch job executes approximately 10 to 20 requests in total.

＊In the event of an error (including HTTP 429), the process halts immediately without auto-retrying. It records the request payload and status code to an audit log and alerts the responsible team via email.

Please let us know if you need any additional information.

Best,

Akari

2026年8月21日(金) 0:35 Bryn Whitcomb <bryn.w...@teads.com>:

--

Akari Tonda Account Manager e | akari...@teads.com m | 090-7420-4643

[Akari Tonda]

Hi Gussa,

Could you please follow up on this?  

Best,

Akari 

2026年8月24日(月) 12:57 Akari Tonda <akari...@teads.com>:

[Danielle Newman]

Hi Akari,

We've tried to recreate the issue on our end but unfortunately are not getting any error. Therefore, could the client please reset their token again and ensure that their details are correct? If they are still facing this error, could you please send us the x-traceid of the request so we can investigate it on the server's side.

Best regards,

Danielle

To view this discussion visit https://groups.google.com/d/msgid/outbrain-amplifyapi/CAKW%3DVYqhGApkGbrW%2B5uSSWtsu_LaaLm%2BgZ_AcSYiT9ouOc84cw%40mail.gmail.com.

--

Danielle Newman Technical Solutions Engineer e | daniell...@teads.com