Occurrences of one exception issue
Paginated raw $exception events belonging to the issue, most recent first — powers the occurrence list and the stack-trace / session panels of the detail view. Each row carries browser / os / url, a session_id for deep-linking to the session replay, and worker-parsed stack_frames (the original string is kept in stack_raw).
curl -X GET "https://mythic-analytics.gulp.workers.dev/client/v1/data/exceptions/issues/example_string/occurrences?location_id=example_string&date_from=2024-12-25&date_to=2024-12-25&hours_back=42&limit=50&offset=0&segment_id=123e4567-e89b-12d3-a456-426614174000&exclude_segment_id=123e4567-e89b-12d3-a456-426614174000" \
-H "Content-Type: application/json" \
-H "X-Location-Id: example_string" \
-H "Authorization: Bearer YOUR_API_TOKEN"
import requests
import json
url = "https://mythic-analytics.gulp.workers.dev/client/v1/data/exceptions/issues/example_string/occurrences?location_id=example_string&date_from=2024-12-25&date_to=2024-12-25&hours_back=42&limit=50&offset=0&segment_id=123e4567-e89b-12d3-a456-426614174000&exclude_segment_id=123e4567-e89b-12d3-a456-426614174000"
headers = {
"Content-Type": "application/json",
"X-Location-Id": "example_string",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.get(url, headers=headers)
print(response.json())
const response = await fetch("https://mythic-analytics.gulp.workers.dev/client/v1/data/exceptions/issues/example_string/occurrences?location_id=example_string&date_from=2024-12-25&date_to=2024-12-25&hours_back=42&limit=50&offset=0&segment_id=123e4567-e89b-12d3-a456-426614174000&exclude_segment_id=123e4567-e89b-12d3-a456-426614174000", {
method: "GET",
headers: {
"Content-Type": "application/json",
"X-Location-Id": "example_string",
"Authorization": "Bearer YOUR_API_TOKEN"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("GET", "https://mythic-analytics.gulp.workers.dev/client/v1/data/exceptions/issues/example_string/occurrences?location_id=example_string&date_from=2024-12-25&date_to=2024-12-25&hours_back=42&limit=50&offset=0&segment_id=123e4567-e89b-12d3-a456-426614174000&exclude_segment_id=123e4567-e89b-12d3-a456-426614174000", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("X-Location-Id", "example_string")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://mythic-analytics.gulp.workers.dev/client/v1/data/exceptions/issues/example_string/occurrences?location_id=example_string&date_from=2024-12-25&date_to=2024-12-25&hours_back=42&limit=50&offset=0&segment_id=123e4567-e89b-12d3-a456-426614174000&exclude_segment_id=123e4567-e89b-12d3-a456-426614174000')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['Content-Type'] = 'application/json'
request['X-Location-Id'] = 'example_string'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
response = http.request(request)
puts response.body
{
"success": true,
"data": [
{
"event_uuid": "example_string",
"timestamp": "2024-12-25T10:00:00Z",
"message": "example_string",
"browser": "Chrome",
"os": "Windows",
"url": "example_string",
"session_id": "example_string",
"distinct_id": "example_string",
"stack_frames": [
{
"function": "example_string",
"file": "example_string",
"line": 42,
"col": 42,
"in_app": true
}
],
"stack_raw": "example_string"
}
],
"rows": 42
}
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"error": "Forbidden",
"message": "You don't have permission to access this resource",
"code": 403
}
{
"error": "Too Many Requests",
"message": "Rate limit exceeded. Please try again later",
"code": 429,
"retryAfter": 3600
}
{
"error": "Error",
"message": "An upstream data service failed",
"code": 502
}
{
"error": "Service Unavailable",
"message": "The service is temporarily unavailable. Please try again later",
"code": 503
}
/exceptions/issues/{id}/occurrencesTarget server for requests. Edit to use your own host.
Agency key (ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need the read scope of the family the route belongs to (people, events, sessions, replays, exceptions, heatmaps or bigquery_export). See Using an mcp_ key over HTTP.
ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need the read scope of the family the route belongs to (people, events, sessions, replays, exceptions, heatmaps or bigquery_export). See Using an mcp_ key over HTTP.
The stable issue_id from the issue list.
Alternative to the X-Location-Id header for agency (ak_) keys. Ignored for secret (sk_) keys.
Start date (YYYY-MM-DD).
End date (YYYY-MM-DD).
Max rows. Default 50, min 1, max 200.
Scope results to members of a saved segment (created via the Segments API). Two independent time filters apply: the segment decides WHICH PEOPLE qualify (a live definition, evaluated at query time — not stored membership), and date_from/date_to decides WHICH OF THEIR ROWS are returned. A person who qualifies today contributes all their sessions/events inside the date window — including ones unrelated to how they qualified; there is no "only rows from while they were a member". For first/last attribution scopes membership runs through the identity graph (a row counts when its distinct_id maps to a matching person); a segment with attribution: "session" instead matches visitors directly against the sessions store ("ever had a session that arrived via X"), with no identity-graph dependency. Composable with all other filters. Unknown or foreign id → 404 segment_not_found.
Scope results OUT — exclude rows from members of a saved segment (the inverse of segment_id, evaluated the same live way). Fully composable with segment_id: scope to one segment and exclude another simultaneously. The primary use is stripping your own QA/test traffic — which is often anonymous, so a rule-based segment (email domain, known ids) catches it with no SDK changes on the client's site. Unknown or foreign id → 404 exclude_segment_not_found.
Location to scope the request to. Required for agency (ak_) keys on the event routes. Ignored for secret (sk_) keys, which resolve their own location, and not used by /export.
Request Preview
Response
Response will appear here after sending the request
Authentication
Bearer token. Agency key (ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need the read scope of the family the route belongs to (people, events, sessions, replays, exceptions, heatmaps or bigquery_export). See Using an mcp_ key over HTTP.
Path Parameters
The stable issue_id from the issue list.
Query Parameters
Alternative to the X-Location-Id header for agency (ak_) keys. Ignored for secret (sk_) keys.
Start date (YYYY-MM-DD).
End date (YYYY-MM-DD).
Max rows. Default 50, min 1, max 200.
Scope results to members of a saved segment (created via the Segments API). Two independent time filters apply: the segment decides WHICH PEOPLE qualify (a live definition, evaluated at query time — not stored membership), and date_from/date_to decides WHICH OF THEIR ROWS are returned. A person who qualifies today contributes all their sessions/events inside the date window — including ones unrelated to how they qualified; there is no "only rows from while they were a member". For first/last attribution scopes membership runs through the identity graph (a row counts when its distinct_id maps to a matching person); a segment with attribution: "session" instead matches visitors directly against the sessions store ("ever had a session that arrived via X"), with no identity-graph dependency. Composable with all other filters. Unknown or foreign id → 404 segment_not_found.
Scope results OUT — exclude rows from members of a saved segment (the inverse of segment_id, evaluated the same live way). Fully composable with segment_id: scope to one segment and exclude another simultaneously. The primary use is stripping your own QA/test traffic — which is often anonymous, so a rule-based segment (email domain, known ids) catches it with no SDK changes on the client's site. Unknown or foreign id → 404 exclude_segment_not_found.
Headers
Location to scope the request to. Required for agency (ak_) keys on the event routes. Ignored for secret (sk_) keys, which resolve their own location, and not used by /export.
Responses
Number of rows returned.