Skip to main content

For AI agents: a Markdown version of this page is at https://docs.snowplow.io/docs/pipeline/collector/configuration-reference.md. The index of all documentation pages is at https://docs.snowplow.io/llms.txt, and the index for this section is at https://docs.snowplow.io/docs/platform/llms.txt.

Collector configuration API reference

This page describes the Console API endpoint that returns a pipeline's Collector configuration, the fields in its response, and the HTTP request headers the Collector accepts. To view or retrieve the configuration step by step, see Check your Collector configuration. For the Self-Hosted Collector's configuration file, see the Collector configuration options.

Parameters​

The endpoint takes two path parameters and returns one JSON object.

Endpoint​

GET https://console.snowplowanalytics.com/api/msc/v1/organizations/{organizationId}/resources/v1/pipelines/{pipelineId}/configuration/collector

GET is the only supported method. Every request needs an Authorization: Bearer {{token}} header; Check your Collector configuration shows how to get the token. The API specification is the normative definition.

NameTypeRequiredDescription
organizationIdUUIDRequired

Your organization ID, from the Manage organization page in Console.

pipelineIdUUIDRequired

The pipeline ID: the second UUID in the browser's address bar when you view the pipeline in Console.

Response fields​

cookieDomains, paths, and cookieAttributes are always present in the response.

NameTypeRequiredDefaultDescription
cookieDomainsobjectRequiredNone

The domains the Collector sets cookies for.

cookieDomains.domainsstring[]RequiredNone

Domains for which Collector cookies are set. May be an empty list.

cookieDomains.fallbackstringOptionalnone

The fallback cookie domain.

pathsobjectRequiredNone

The request paths the Collector accepts.

paths.post.pathsstring[]RequiredNone

Paths that accept Tracker Protocol 2 compatible POST requests.

paths.redirect.enabledbooleanRequiredNone

Whether redirect-based tracking is enabled.

paths.redirect.pathsstring[]RequiredNone

Paths that support redirect-based tracking.

paths.webhook.pathsstring[]RequiredNone

Paths for events sent in a GET or POST request with an Iglu-compatible event payload.

cookieAttributesobjectRequiredNone

Attributes of the Collector cookie.

cookieAttributes.securebooleanRequiredNone

Whether secure connections are enforced.

cookieAttributes.httpOnlybooleanRequiredNone

Whether the cookie is inaccessible to non-HTTP requests.

cookieAttributes.sameSite'lax' | 'none' | 'strict'RequiredNone

The cookie's SameSite attribute.

blockUnencryptedbooleanOptionalfalse

Whether the Collector blocks unencrypted traffic.

Example​

A response for a pipeline with one fallback cookie domain and redirect tracking enabled:

json
{
"cookieDomains":
{
"fallback": "mydomain.com",
"domains": []
},
"paths": {
"post": {
"paths": []
},
"webhook": {
"paths": []
},
"redirect": {
"paths": [],
"enabled": true
}
},
"cookieAttributes": {
"secure": true,
"sameSite": "None",
"httpOnly": false
},
"blockUnencrypted": false
}

HTTP request headers​

The Collector collects all standard HTTP headers. To add header values to your events, configure the HTTP header extractor enrichment for the headers you want.

These two headers also change how the Collector handles a request:

HeaderAllowed valuesDescription
Content-Typeapplication/jsonSee MDN Content-Type
SP-Anonymous*Enables server-side anonymization, so the Collector doesn't collect the user's IP address or network user ID

The Collector also collects the cookies sent in the Cookie header. To attach cookie values to your events, use the cookie extractor enrichment.

Was this page helpful?