Query Error Symbolication
Resolve the stack frames of one error signature to a code location.
Separate from /error-types/detail on purpose. It leaves the process to
fetch the customer's bundle, so it is slower than every other analytics
read and it fails in ways the drill-down must survive. The dashboard asks
for it after the detail has rendered, and a frame that cannot be resolved
comes back with a status rather than an error.
Authentifizierung
bearerAuth API token generated from the fastmon dashboard (Account → API Token) or at organization level (fmo_…, one that outlives its creator). Send as Authorization: Bearer fm_... or paste the full token (including its prefix) into the Authorize dialog.
In: header
Pfad-Parameter
uuidRequest-Body
application/json
Request for /analytics/error-types/symbolicate.
Carries the same identity as the error detail. There is deliberately no URL parameter: the frames come from what we stored for this fingerprint, so a caller cannot point our fetcher at a host of their choosing.
Response-Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/organizations/497f6eca-6276-4993-bfeb-53cbbbba6f08/analytics/error-types/symbolicate" \ -H "Content-Type: application/json" \ -d '{ "time_range": { "from": "2019-08-24T14:15:22Z", "to": "2019-08-24T14:15:22Z" }, "fingerprint": "string" }'{ "frames": [ { "index": 0, "host": "string", "path": "string", "line": 0, "column": 0, "status": "resolved", "module_id": "", "method": "", "object": "", "property": "", "snippet": "", "caret_at": 0, "near_boundary": false, "rethrow": false } ], "execution_time_ms": 0}