api.stigg.io
and edge.api.stigg.io
), you can route Stigg SDK traffic through your own backend proxy.
This guide shows how to configure your frontend SDK and proxy server to forward requests to Stigg correctly.
https://api.stigg.io
https://edge.api.stigg.io
baseUri
: The proxy endpoint that forwards requests to https://api.stigg.io
.baseEdgeUri
: The proxy endpoint that forwards requests to https://edge.api.stigg.io
.https://api.stigg.io
. Similarly, any requests related to the Edge API must be forwarded to https://edge.api.stigg.io
. This typically involves exposing two distinct paths or routes on your proxy—one for each upstream destination.
In addition to routing, the proxy must preserve the full set of headers sent by the Stigg SDK. Specifically, the following headers must be included in the forwarded request without modification:
X-API-KEY
: Used to authenticate the SDK with StiggX-API-VERSION
: Specifies which API version the SDK is usingX-CUSTOMER-KEY
: Identifies the customer associated with the request