504 Gateway Time-out with events API endpoint

Hi everyone, we are receiving the following error:

Error(s): Could not handle API response because of malformed JSON data: "

504 Gateway Time-out

The server didn’t respond in time. " (504)

with the following request:

curl -L -X POST ‘https://iconmedia.piwik.pro/api/analytics/v1/events/
-H ‘User-Agent: python-requests/2.22.0’
-H ‘Accept-Encoding: gzip, deflate’
-H ‘Accept: /
-H ‘Connection: keep-alive’
-H ‘Authorization: Bearer REMOVED’
-H ‘Content-Length: 1207’
-H ‘Content-Type: application/json’
–data-raw ‘{
“format”:“json”,
“date_from”:“2021-11-24”,
“date_to”:“2021-11-24”,
“website_id”:“REMOVED”,
“limit”:100000,
“offset”:0,
“columns”:[
{
“column_id”:“website_name”
},
{
“column_id”:“campaign_name”
},
{
“column_id”:“source”
},
{
“column_id”:“referrer_url”
},
{
“column_id”:“ipv4_address”
},
{
“column_id”:“ipv6_address”
},
{
“column_id”:“medium”
},
{
“column_id”:“referrer_type”
},
{
“column_id”:“visitor_returning”
},
{
“column_id”:“visitor_days_since_first_session”
},
{
“column_id”:“visitor_days_since_last_session”
},
{
“column_id”:“visitor_days_since_order”
},
{
“column_id”:“device_model”
},
{
“column_id”:“device_type”
},
{
“column_id”:“device_brand”
},
{
“column_id”:“operating_system”
},
{
“column_id”:“browser_name”
},
{
“column_id”:“location_country_name”
},
{
“column_id”:“location_city_name”
},
{
“column_id”:“location_subdivision_1_name”
},
{
“column_id”:“location_metro_code”
},
{
“column_id”:“event_type”
},
{
“column_id”:“revenue”
},
{
“column_id”:“revenue_discount”
},
{
“column_id”:“revenue_shipping”
},
{
“column_id”:“revenue_subtotal”
},
{
“column_id”:“revenue_tax”
},
{
“column_id”:“order_id”
},
{
“column_id”:“custom_event_category”
},
{
“column_id”:“session_total_custom_events”
}
]
}’

Would someone know how to handle this server error? I am happy to provide the website_id in a private message!

Thanks in advance!

Hi @Lorenz_Weinzierl, It was a global issue that affected a lot of users. Our engineers were working on the issue since yesterday and it is resolved now.
Let us know if you still experience any issues with the API.

Thanks for the info Jarek! I can confirm that it works again