> ## Documentation Index
> Fetch the complete documentation index at: https://docs.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API Request Tracing

Storefront Gateway utilizes distributed tracing techniques compliant with the [OpenTracing](https://opentracing.io/) specification.

Distributed tracing is designed to help profile and monitor applications, especially those built upon modern software architectures (such as microservices). It assists in tracking the fulfillment of a client's request across different one or more (micro)services. The result of this tracing is visible to clients in the form of a `X-B3-TraceId` header returned as part of requests to Storefront Gateway with a unique string generated on each request as its value.

However, customers that integrate with Storefront Gateway (especially in cases where machine-to-machine interactions are required) may already be using distributed tracing internally, and so wish to use their own internally generated value with Storefront Gateway, instead of Storefront Gateway generating a trace identifier of its own. Storefront Gateway supports accepting the `X-B3-TraceId` header with each request, using the value provided as the trace identifier.

```
**REQUEST**
GET /account/1
```

```
**RESPONSE**
Header: X-B3-TraceId = dd950f07f143ebcb 
{ 
   "id": 1, 
   "displayName": "Entity display name", 
   "status": "activated", 
   "type": "com.uxpsystems.ulm.entity.RegularType" 
}
```

**Parent topic:**[HTTP Headers](c_connectHTTPheaders)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.