Server-Side Panorama ID API for Web

OVERVIEW

The Server-Side Panorama ID API for web is a real-time server-side API endpoint designed to return the assigned Panorama ID for an IP and useragent sent into the request. This page will outline the technical details of the REST endpoint and provide a few examples.

---

HTTP POST Endpoint

https://sid.crwdcntrl.net/sid

JSON Object Details

Request JSON Details

Key	Data Type	Required?	Description
client_id	Integer	Yes	Static value assigned to you by Lotame.
ip_address	String	Yes	IP address in IPv4 or IPv6 format.
user_agent	String	Yes	Client user-agent string.
consent	Object	Yes	See Consent Object JSON Details

 

Consent Object JSON Details

Key	Data Type	Required?	Description
consent.gdpr_applies	Boolean	Yes, unless using lotame_consent value below	True or False to indicate whether the originating consumer interaction is subject to enforcement of the GDPR.
consent.gdpr_consent	String	Yes, unless using lotame_consent value below	Consent string as specified in the TCFv2 spec
consent.lotame_consent	Boolean	Yes, unless using GDPR values above	True or False to indicate whether you have obtained consent

 

Response JSON Details

Key	Data Type	Description
pano_id	String	Lotame Panorama ID.
expiry_ts	Long	Timestamp in ms relative to the epoch. Clients should not request the same IP / useragent combo until after this expiration time.
errors	Array of Integers	May contain zero-to-all of the following error codes (with the description after the hyphen): * 110 - Invalid JSON in the request body * 111 - Processing disallowed due to lack of consent relative to configured consent policy. see no_consent parameter below for details. * 112 - Unspecified Error * 113 - TCF is required, but the provided string lacks purpose When present, expiry_ts will be reduced. * 114 - gdpr_consent is required, but was not supplied.
no_consent	String	One of the following strings (with the description after the hyphen): * TCF - Processing disallowed due to missing requirements in the TCFv2 string. * LOTAME_ACTIVE_CONSENT - Processing disallowed due to no consent via Lotame Active Consent * NO_CORE_CONSENT - Processing disallowed due to no consent via Lotame Consent

Example JSON Objects

Request Example

{
  "ip_address": "192.168.0.20",
  "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36",
  "client_id": 123,
  "consent": {
    "gdpr_applies": true,
    "gdpr_consent": "CPoB4-bPoB4-bABAMBFRACCgAAAAAAAAAAYgAAAAAAAA"
  }
}

Response Examples

Success

{
  "pano_id": "aa24ca9e5712f0411ac79902056616d539383860cb22fe55608b9920d7e6c659",
  "expiry_ts": 1678476158619
}

Failure

{
  "expiry_ts": 1678476158619,
  "errors": [111],
  "no_consent": "TCF"
}