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

Segment Pixel Tracking API

The Segment Pixel Tracking API provides a way to collect analytics data using image pixel requests, which is useful in environments where JavaScript cannot execute, such as email clients. It supports identify, track, page, screen, group, and alias calls through pixel endpoints under the api.segment.io domain. This API is particularly suited for tracking email opens, ad impressions, and other contexts where embedding a tracking pixel is the only viable data collection method.

Segment Pixel Tracking API is one of 23 APIs that Twilio Segment publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Analytics, Email, Pixel, and Tracking. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.

This API exposes 6 operations across 6 paths. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://platform.segmentapis.com/v1beta.

6 operations 6 paths 0 schemas 6 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.segment.io
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Segment Pixel Tracking API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Segment Config API access token. Note that as of early 2024, Segment has stopped issuing new Config API tokens.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 6 GET. Each is listed below with its method, path, parameters, and response codes.

Pixel Tracking 6

Pixel-based tracking endpoints that accept data via query parameters and return a transparent 1x1 GIF image. All data is passed as a base64-encoded JSON object in the data query p…

GET
/pixel/identify
Identify via pixel
pixelIdentify 1 param → 200
GET
/pixel/track
Track via pixel
pixelTrack 1 param → 200
GET
/pixel/page
Page via pixel
pixelPage 1 param → 200
GET
/pixel/screen
Screen via pixel
pixelScreen 1 param → 200
GET
/pixel/group
Group via pixel
pixelGroup 1 param → 200
GET
/pixel/alias
Alias via pixel
pixelAlias 1 param → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

segment-pixel-tracking-api-openapi.yml Raw ↑

Other APIs Twilio Segment publishes across the network.

segment Alias API
segment Batch API
segment Catalog API
segment Destinations API
segment Events API
segment External IDs API
segment Functions API
segment Group API
segment Identify API
segment Labels API
segment Links API
segment Page API
Where this information came from

This is an independent, third-party profile of Segment Pixel Tracking 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.