Stape API 409 Error Status for Outgoing Request Logs

Google Tag Manager Server Container
1

Hi, i am currently experiencing issues with the Stape API and was wondering if anyone else may have ran into similar issues.
I am trying to get outbound logs via the /monitoring/logs/outgoing/detailed (same for /aggregated) endpoint. I tried this for 2 of my containers which have outgoing logs enabled.
When I do - no matter if via a n8n Request node or the “try out” in the stape.io API doc - I get an 409 “Conflict” server status.
Since this status code is not listed as a possible output and did not find any reference to it anywhere in this forum or the web, I was wondering if maybe someone has seen this error and fixed it.

So far I am certain of these things:

  • I can use my API key to access other API endpoints
  • the container identifiers are correct
  • the containers have outgoing logs for the time ranges I try to access
  • I used correct timestamps for filtering since I copied them from the requests made by the outgoing request feature in the frontend

test-response-stape-eu
test-response-stape-eu1500×717 120 KB

2

Hi @thebigcagency

Thank you for bringing this to our attention!

Retrieving logs via the Stape API is not permitted for customers due to the heavy load if users attempt to retrieve a large number of logs.
These endpoints accidentally appeared in the public API and will be removed from there in the near future.

At the same time, we are already working on a feature that will allow you to automatically upload all logs to an AWS/GCP bucket, from where they can be sent to any tool you need.

3

Thanks for the reply. I’ll check back to see when the feature is added.