How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Sumo Logic

Sumo Logic traces API

Traces APIThe Traces API allows you to browse traces collected in the system. You can execute queries to find traces matching provided search criteria as well as gather detailed information about individual traces and spans. For more information, see [View and investigate traces](https://help.sumologic.com/docs/apm/traces/view-and-investigate-traces).

Documentation Provider Profile APIs.io OpenAPI GitHub

Sumo Logic traces API is one of 61 APIs that Sumo Logic publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Traces. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 15 operations across 15 paths, and defines 41 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 10 base URLs: https://api.au.sumologic.com/api/, https://api.ca.sumologic.com/api/, https://api.de.sumologic.com/api/, https://api.eu.sumologic.com/api/, https://api.fed.sumologic.com/api/, https://api.jp.sumologic.com/api/, https://api.kr.sumologic.com/api/, https://api.in.sumologic.com/api/, https://api.sumologic.com/api/, https://api.us2.sumologic.com/api/.

15 operations 15 paths 41 schemas 1 DELETE13 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.sumologic.com/api
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Sumo Logic traces API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 15

Across 15 paths, the API surfaces 15 operations — 1 DELETE, 13 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

traces 15

Traces API The Traces API allows you to browse traces collected in the system. You can execute queries to find traces matching provided search criteria as well as gather detailed…

POST
/v1/tracing/tracequery
Run A Trace Search Query Asynchronously.
createTraceQuery body → 200default
DELETE
/v1/tracing/tracequery/{queryId}
Cancel A Trace Search Query.
cancelTraceQuery 1 param → 204default
GET
/v1/tracing/tracequery/{queryId}/status
Get A Trace Search Query Status.
getTraceQueryStatus 1 param → 200default
GET
/v1/tracing/tracequery/{queryId}/rows/{rowId}/traces
Get Results Of A Trace Search Query.
getTraceQueryResult 4 params → 200default
GET
/v1/tracing/metrics
Get Trace Search Query Metrics.
getMetrics → 200default
GET
/v1/tracing/tracequery/fields
Get Filter Fields For Trace Search Queries.
getTraceQueryFields → 200default
GET
/v1/tracing/tracequery/fields/{field}/values
Get Trace Search Query Filter Field Values.
getTraceQueryFieldValues 5 params → 200default
GET
/v1/tracing/traces/{traceId}
Get Trace Details.
getTrace 1 param → 200default
GET
/v1/tracing/traces/{traceId}/exists
Check If The Trace Exists.
traceExists 1 param → 200default
GET
/v1/tracing/traces/{traceId}/spans
Get A List Of Trace Spans.
getSpans 3 params → 200default
GET
/v1/tracing/traces/{traceId}/traceEvents
Get A List Of Events (without Their Attributes) Per Span For A Trace.
getTraceLightEvents 3 params → 200default
GET
/v1/tracing/traces/{traceId}/criticalPath
Get A Critical Path Of A Trace.
getCriticalPath 3 params → 200default
GET
/v1/tracing/traces/{traceId}/criticalPath/breakdown/service
Get A Critical Path Service Breakdown Of A Trace.
getCriticalPathServiceBreakdown 1 param → 200default
GET
/v1/tracing/traces/{traceId}/spans/{spanId}
Get Span Details.
getSpan 2 params → 200default
GET
/v1/tracing/traces/{traceId}/spans/{spanId}/billingInfo
Get Span Billing Details.
getSpanBillingInfo 2 params → 200default

Schemas 41

The contract defines 41 schemas that model the data the API accepts and returns. The most detailed are TraceSpan (16 properties), TraceDetail (8 properties), TraceFieldDetail (6 properties), SpanPathSegment (6 properties). Each schema is shown below with its type and property counts.

CriticalPathServiceBreakdownResponse
object
2 properties 2 required
CriticalPathResponse
object
2 properties 1 required
SpanEvent
Span event containing all information (in particular attributes).
TraceDetail
object
8 properties 1 required
OrderBy
object
2 properties 2 required
TraceFieldValuesResponse
object
3 properties 2 required
TraceQueryResultResponse
object
2 properties 1 required
TraceMetricDetail
object
3 properties 2 required
AsyncTraceQueryRow
object
3 properties 2 required
TraceQueryExpression
object
Base query expression object.
1 property 1 required
ResolvableTimeRange
object
1 property 1 required
ErrorResponse
object
2 properties 2 required
LightSpanEvent
object
Light version of Span Event, without the attributes.
2 properties 2 required
CriticalPathServiceBreakdownSummary
object
3 properties 3 required
CriticalPathServiceBreakdownElementBase
object
3 properties 1 required
SpanEventAttribute
object
2 properties
SpanPathSegment
object
6 properties 4 required
AsyncTraceQueryRequest
object
2 properties 2 required
ServiceType
string
Defines type of service.
ErrorDescription
object
4 properties 2 required
TraceSpanInfo
object
1 property 1 required
TraceSpan
object
16 properties 5 required
TraceFieldsResponse
object
1 property 1 required
TraceMetricsResponse
object
1 property 1 required
CriticalPathServiceBreakdownElementDetail
EventAttributeValue
object
1 property 1 required
TraceSpanStatus
object
2 properties 1 required
TraceQueryRowStatus
object
4 properties 3 required
TraceSpanBillingInfo
object
2 properties 2 required
CreateTraceQueryResponse
object
1 property 1 required
DoubleTracingValue
TraceQueryStatusResponse
object
2 properties 2 required
SpanLink
object
Details of the linked span.
2 properties 2 required
TracingValue
object
1 property 1 required
TraceSpanCriticalPathContribution
object
2 properties 2 required
TraceLightEventsResponse
object
2 properties
TraceFieldDetail
object
6 properties 3 required
TraceSpanDetail
NoTraceFieldValuesReason
object
2 properties 2 required
TraceSpansResponse
object
3 properties 2 required
TraceExistsResponse
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sumo-logic-traces-api-openapi.yml Raw ↑

Other APIs Sumo Logic publishes across the network.

Sumo Logic accessKeyManagement API
AE Profile APIs.io
Sumo Logic accountManagement API
AE Profile APIs.io
Sumo Logic appManagement API
AE Profile APIs.io
Sumo Logic appManagementV2 API
AE Profile APIs.io
Sumo Logic archiveManagement API
AE Profile APIs.io
Sumo Logic budgetManagement API
AE Profile APIs.io
Sumo Logic connectionManagement API
AE Profile APIs.io
Sumo Logic contentManagement API
AE Profile APIs.io
Sumo Logic contentPermissions API
AE Profile APIs.io
Sumo Logic dashboardManagement API
AE Profile APIs.io
Sumo Logic dataDeletionRules API
AE Profile APIs.io
Sumo Logic dataMaskingManagement API
AE Profile APIs.io
#Traces
← Back to S APIs
API Details
ID
sumo-logic:sumo-logic-traces-api
Base URL
https://api.sumologic.com/api
Docs
https://help.sumologic.com/docs/api/
Provider
Sumo Logic
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=sumo-logic-traces-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/sumo-logic-traces-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Sumo Logic traces API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.