500 Internal Server Error on POST /reports/content Endpoint

[amadeus]

Hi Outbrain API Team,

I hope you're having a good week.

I am trying to get a list of active campaign IDs using the reporting endpoint, but I'm consistently receiving a 500 Internal Server Error with the message: "Our servers encountered an error while processing your request".

I have already done extensive troubleshooting and believe the issue may be on the server-side. Here is what I have confirmed:

• Successful Authentication: I can successfully make a GET request to the /amplify/v0.1/marketers/{my_marketer_id} endpoint and receive a 200 OK response with my correct marketer data. This confirms my authentication token and connection are working perfectly.

• Correct Headers: I am including both the Content-Type: application/json and a unique AMPLIFY-REQUEST-ID header in my POST request, as required by the documentation.

• Correct Body and Filter: I am using the enabledCampaignsOnly: true filter, which was confirmed in your "Upcoming Change" announcement from December 2024. I have also tried hardcoding the dates to ensure the format is correct.

The issue seems to be isolated specifically to the /reports/content endpoint. Since my GET request works but the POST request fails, could you please investigate why this specific endpoint is returning a 500 error?

Here is the simple, hardcoded request that is failing:

Method: POST

URL: https://api.outbrain.com/amplify/v0.1/reports/marketers/{my_marketer_id}/content

Headers:

Content-Type: application/json OB-TOKEN-V1: [My_Valid_Token] AMPLIFY-REQUEST-ID: {a_sample_request_id}

Body:

JSON

{ "from": "2025-10-01", "to": "2025-10-10", "enabledCampaignsOnly": true, "includeFields": ["campaignId"] }

Any help you could provide would be greatly appreciated.

Thank you!

[Marta Bernasconi]

Hello,

Thank you for reaching out! Hope you are having a good week too.

To get a list of the active campaigns in the reporting endpoint, you can use the following URL:

/reports/marketers/id/campaigns?from=2025-10-01&to=2025-10-10&enabledCampaignsOnly=true

In this case, there are a few aspects to keep in mind:

- The parameters from, to and enabledCampaignsOnly must be set in the URL (not in the body) of the request

- This endpoint requires a GET method (not POST), as you can check in the documentation here

- Please remove AMPLIFY-REQUEST-ID in the request header

- With this call, you will get performance statistics as well for the listed campaigns. 

As for the endpoint /reports/marketers/{my_marketer_id}/content this is not a valid endpoint. 

We have the following endpoint:

/reports/marketers/id/promotedContent

which allows you to retrieve performance statistics by promoted link (documentation for this endpoint is here). However, if your goal is to list the campaigns, you can refer to the first endpoint I shared. 

Please let me know if you still encounter any error despite the modifications recommended above or if you have any questions!

Best,

Marta

On Mon, Oct 20, 2025 at 1:00 PM amadeus <auracher...@gmail.com> wrote:

Teads couldn't recognize this email as this is the first time you received an email from this sender auracher.amadeus @ gmail.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/cf0d71ca-4769-432c-8d2b-52000ea82200n%40googlegroups.com.

--

Marta Bernasconi 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.

[amadeus]

Hi Marta,

Thank you so much for your help!

Your instructions were perfect. I've changed my request to use the GET method on the /reports/marketers/id/campaigns endpoint with the parameters in the URL, and it's working perfectly now.

I really appreciate you clearing that up for me.

Best regards,