It is the only way we can trace your specific request. We will not manually sift through ... logged requests to find your error.
what to include
-The X-Request-ID
-HTTP method and endpoint (include query parameters if any)
-HTTP status code
-The JSON request body (only for POST/PATCH)
-Expected behavior and actual behavior
-Steps to reproduce
Not all fields apply to every endpoint, but provide as much detail as possible.
what NOT to include
Do not attach files.
Do not include your X-Management-Token. Redact it from your request bodies before sending.
your code
Double check that the error is actually on our end before sending a report. We are not your programmers and we won't fix your code (unless it's a very simple mistake).
This API is maintained by a very small team for free. Do not expect an instant reply!
We typically only respond to the first person who reports a specific bug. If you do not hear back the issue is likely already known and being worked on.
example report
Subject: POST /regex/test returning 400 - Request ID: ...
Body:
Request ID: ... Endpoint: POST /v1/regex/test Status: 400 Time: 2026-08-18 ~11:30 UTC Request: {"pattern":"[","text":"hello","flags":""}
Expected: json error explaining that the regex pattern is invalid. Actual: server returned HTTP 500 instead of 400.