HTTP 500 on All Reporting Endpoints - No AMPLIFY-REQUEST-ID Returned

[Ezra Israelov]

Hi Outbrain API Community,

I am building a reporting integration between the Outbrain Amplify API and Google Sheets to automate daily performance reporting for my clients. I have been granted API access and my token works correctly for all management endpoints, but every single reporting/performance endpoint returns HTTP 500.

Account Details:

Account ID: 0080871a18aec84799191b0c9759a551e5
Marketer ID used for testing: 0032cda68d50851c78562c37e43dc3affe
What Works (HTTP 200):

GET /marketers ✅
GET /marketers/{id} ✅
GET /marketers/{id}/campaigns ✅

What Fails (HTTP 500):

Every reporting endpoint returns 500 regardless of parameters:

GET /reports/campaigns-performance?from=2026-03-16&to=2026-03-16&marketerId={id}
GET /reports/publishers-performance?from=2026-03-16&to=2026-03-16&marketerId={id}
GET /reports/promoted-links-performance?from=2026-03-16&to=2026-03-16&marketerId={id}
GET /reports/sections-performance?from=2026-03-16&to=2026-03-16&marketerId={id}
GET /reports/marketer-performance?from=2026-03-16&to=2026-03-16&marketerId={id}
GET /marketers/{id}/campaigns/performanceByTime?from=2026-03-16&to=2026-03-16&breakdown=daily
Variations Tested - All Return 500:

With and without the marketerId parameter
With enabledCampaignsOnly=false
With different date ranges (current month, past months, year 2025)
With Accept: application/json header
With Content-Type: application/json header
With different marketer IDs
Without any query parameters at all
Response Body:

{"message": "Our servers encountered an error while processing your request"}

Response Headers (critical findings):

{
  "Via": "1.1 varnish",
  "x-served-by": "cache-pdk-kfty8610085-PDK",
  "fastly-restarts": "1",
  "x-cache": "MISS"
}

Two important observations from the headers:

fastly-restarts: 1 — Fastly automatically retried the request and still received 500, confirming the backend consistently fails.
No AMPLIFY-REQUEST-ID is returned — This means the request reaches the CDN layer but never makes it to the Outbrain application server, so we cannot provide a request ID for investigation.
Our Conclusion:

The token has sufficient authorization to pass through the CDN (no 401 or 403 is returned), but the reporting service backend crashes before processing the request and before generating an AMPLIFY-REQUEST-ID. This appears to be a server-side configuration issue specific to our account or token, not a client-side error.

We have already contacted Outbrain support directly and were told we have full API access. However, the problem persists.

Questions:

1. Does reporting API access require a separate configuration or activation beyond the standard API token?
2. Is there a known issue with the reporting service for certain account types?
3. Is there an alternative endpoint or authentication method required for performance data?
4. Can someone from the Outbrain team investigate why the reporting service returns 500 with no AMPLIFY-REQUEST-ID for our account?
5. Any help from the community or Outbrain team would be greatly appreciated.

Thank you

[Nika Krnc]

Hi Ezra,

Reviewing the endpoints returning a 500 error, it seems they aren't structured correctly. 

For example, the endpoint for publisher performance should be:  reports/marketers/id/publishers

and not as you provided it above: /reports/publishers-performance?from=2026-03-16&to=2026-03-16&marketerId={id} 

You can also refer to the API documentation here.

The same applies to the other endpoints you provided. Please refer to the documentation here to find the appropriate endpoint for different performance reporting metrics, as well as different breakdown options by time.

Let me know, if you have any further questions.

Best,

Nika

On Tue, Mar 17, 2026 at 12:34 PM Ezra Israelov <ez...@inno.co.il> wrote:

Teads couldn't recognize this email as this is the first time you received an email from this sender ezra @ inno.co.il

--
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/41f91edd-39ce-40bc-9aa3-6a42be2740e3n%40googlegroups.com.

--

Nika Krnc Technical Solutions Engineer e | nika...@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.