Customer.io Screen API
Record screen views from mobile applications.
Record screen views from mobile applications.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/customer-io-screen-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
version: 1.0.0
title: Pipelines Screen API
description: '# Overview
In general, you''ll consume this API through one of our source libraries—our JavaScript client library or any of our server packages.'
servers:
- url: https://cdp.customer.io/v1
description: The base URL for all Data Pipelines calls in our United States (US) region.
- url: https://cdp-eu.customer.io/v1
description: The base URL for all Data Pipelines calls in our European Union (EU) region.
tags:
- name: Screen
paths:
/screen:
post:
operationId: screen
summary: Track mobile screenviews
description: Sends a screen view event for mobile devices. Screen events help you understand the screens that people use in your app. You should send a screen call whenever a user requests a page of your app.
servers:
- url: https://cdp.customer.io/v1
description: This is a Data Pipeline API.
security:
- Basic-Auth: []
parameters:
- name: X-Strict-Mode
in: header
description: 'When set to `1`, enables strict validation that returns proper HTTP error codes (400/401) for validation failures. When not set or set to any other value, the API operates in permissive mode, logging errors but returning HTTP 200. [Learn more](/integrations/api/track-vs-cdp-api#pipelines-strict-mode)
'
required: false
schema:
type: string
enum:
- '1'
example: '1'
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/screen'
x-codeSamples:
- lang: json
label: JSON
source: "{\n \"anonymousId\": \"507f191e810c19729de860ea\",\n \"context\": {\n \"ip\": \"8.8.8.8\"\n },\n \"integrations\": {\n \"All\": true,\n \"Salesforce\": false\n },\n \"messageId\": \"022bb90c-bbac-11e4-8dfc-aa07a5b093db\",\n \"name\": \"feed\",\n \"properties\": {\n \"subscriptions\": [\n \"baseball\",\n \"basketball\"\n ]\n },\n \"receivedAt\": \"2015-02-23T22:28:55.387Z\",\n \"sentAt\": \"2015-02-23T22:28:55.111Z\",\n \"timestamp\": \"2015-02-23T22:28:55.111Z\",\n \"type\": \"screen\",\n \"userId\": \"97980cfea0067\",\n \"version\": 1.1\n}"
- label: Curl
lang: shell
source: "curl --request POST \\\n --url https://cdp.customer.io/v1/screen \\\n -u api_key: \\\n -H 'content-type: application/json' \\\n --data-raw '\n {\n \"userId\": \"f4ca124298\",\n \"name\": \"feed\",\n \"properties\": {\n \"subscriptions\": [\n \"baseball\",\n \"basketball\"\n ]\n }\n }'\n"
responses:
'200':
$ref: '#/components/responses/200'
tags:
- Screen
components:
schemas:
userId:
x-scalar-ignore: true
type: string
description: The unique identifier for a person. This value should be unique across systems, so you recognize the same person in your sources _and_ destinations.
example: 241ma8mf4a
mobile_common_fields:
x-scalar-ignore: true
allOf:
- $ref: '#/components/schemas/common_fields'
- type: object
properties:
context:
$ref: '#/components/schemas/context_mobile'
context_mobile:
x-scalar-ignore: true
description: A dictionary of context about a source call/event, like the user’s IP address or locale. Context is automatically collected by our source libraries.
title: Mobile
allOf:
- $ref: '#/components/schemas/context_common'
- type: object
description: Fields included in events from mobile libraries.
properties:
app:
type: object
description: 'Contains information about the mobile app the event originated from, automatically collected by our mobile libraries when possible.
'
properties:
name:
type: string
description: The name of the app.
version:
type: string
description: The version of the app the call originated from.
build:
type: string
description: The specific build number in the app.
namespace:
type: string
description: The app's namespace.
device:
type: object
description: 'Contains information about the device the event originated from.
'
properties:
id:
type: string
description: The device ID.
advertisingId:
type: string
description: The advertising ID is a unique, anonymous ID for advertising.
manufacturer:
type: string
description: The device manufacturer.
model:
type: string
description: The device model.
name:
type: string
description: The device name.
type:
type: string
description: The device type—android, iOS, etc.
enum:
- android
- ios
version:
type: string
description: The firmware version for the device.
network:
type: object
description: Information about the current network connection, containing `bluetooth`, `carrier`, `cellular`, and `wifi`. If the `context.network.cellular` and `context.network.wifi` fields are empty, then the user is offline.
properties:
bluetooth:
type: boolean
description: Lets you know if bluetooth is enabled on a device.
carrier:
type: string
description: The cellular carrier the phone uses.
cellular:
type: boolean
description: Indicates whether the device's cellular connection is enabled or not.
wifi:
type: boolean
description: Indicates whether a device's wifi connection is enabled or not.
os:
type: object
description: 'Dictionary of information about the operating system, containing `name` and `version`.
'
properties:
name:
type: string
description: The operating system running on the device.
version:
type: string
description: The version of the OS running on the device.
context_common:
x-scalar-ignore: true
type: object
description: Contains contextual information about the event.
properties:
active:
type: boolean
description: 'Whether a user is active.
This is usually used when you send an .identify() call to update the traits independently of when you''ve “last seen” a user.
'
ip:
type: string
description: The user's IP address. This isn't captured by our libraries, but by our servers when we receive client-side events (like from our JavaScript source).
locale:
type: string
description: The locale string for the current user, e.g. `en-US`.
userAgent:
type: string
description: The user agent of the device making the request
channel:
type: string
enum:
- browser
- server
- mobile
description: The channel the event originated from.
integrations:
x-scalar-ignore: true
type: object
description: 'Contains a list of booleans indicating the integrations that are enabled (true) or disabled (false). By default, all integrations are enabled (returning an empty object). Set `"All": false` to reverse this behavior.
'
additionalProperties:
type: boolean
x-additionalPropertiesName: Enabled/Disabled integrations
example:
All: true
Salesforce: false
anonymousId:
x-scalar-ignore: true
type: string
description: A unique substitute for a User ID in cases when you don’t have an absolutely unique identifier. Our libraries generate this value automatically to help you track people before they sign up, log in, provide their email, etc.
example: c0e5cae6-6f04-46e4-97a8-25076e8bdc0b
common_fields:
x-scalar-ignore: true
type: object
properties:
integrations:
$ref: '#/components/schemas/integrations'
messageId:
type: string
description: A unique identifier for a Data Pipelines call, ensuring that each individual event is unique. This is set by Customer.io
receivedAt:
type: string
format: date-time
readOnly: true
description: The ISO-8601 timestamp when Data Pipelines receives an event.
sentAt:
type: string
format: date-time
description: The ISO-8601 timestamp when a library sends an event to Data Pipelines.
originalTimestamp:
type: string
format: date-time
description: In general, you can use `timestamp` rather than this field if you want to back-date events. This is the timestamp on the client device you invoke a call or the timestamp value you manually passed in a server-side library call.
timestamp:
type: string
format: date-time
description: The ISO-8601 timestamp when the event originally took place. This is mostly useful when you backfill past events. If you're not backfilling data, you can leave this field empty and we'll use the current time or server time.
type:
readOnly: true
type: string
enum:
- identify
- group
- track
- page
- screen
- alias
description: The type of source event. This is implicit and set by Customer.io based on the endpoint/method you use (e.g. `identify`).
version:
readOnly: true
type: number
description: The version of the API that received the event, automatically set by Customer.io.
screen:
x-scalar-ignore: true
oneOf:
- title: Known User
allOf:
- type: object
required:
- userId
properties:
userId:
$ref: '#/components/schemas/userId'
type:
type: string
enum:
- screen
description: The event type. This is set automatically by the request method/endpoint.
name:
type: string
description: The name of the screen the person visited.
example: home
properties:
type: object
description: Additional properties for your screen.
additionalProperties:
x-additionalPropertiesName: Screen Properties
- $ref: '#/components/schemas/mobile_common_fields'
- title: Anonymous User
allOf:
- type: object
required:
- anonymousId
properties:
anonymousId:
$ref: '#/components/schemas/anonymousId'
type:
type: string
enum:
- screen
description: The event type. This is set automatically by the request method/endpoint.
name:
type: string
description: The name of the screen the person visited.
example: home
properties:
type: object
description: Additional properties for your screen.
additionalProperties:
x-additionalPropertiesName: Screen Properties
- $ref: '#/components/schemas/mobile_common_fields'
example:
anonymousId: 507f191e810c19729de860ea
context:
ip: 8.8.8.8
integrations:
All: true
Salesforce: false
messageId: 022bb90c-bbac-11e4-8dfc-aa07a5b093db
name: feed
properties:
subscriptions:
- baseball
- basketball
receivedAt: '2015-02-23T22:28:55.387Z'
sentAt: '2015-02-23T22:28:55.111Z'
timestamp: '2015-02-23T22:28:55.111Z'
type: screen
userId: 97980cfea0067
version: 1.1
responses:
'200':
description: A successful request returns an empty object response.
securitySchemes:
Basic-Auth:
type: http
scheme: basic
description: 'The Data Pipelines API uses a basic authentication scheme with your API key. Because basic authorization typically expects a username and password combination, you''ll use the API Key as the username and leave the password blank—base64 encoding your credentials in the format `API_key:`.
'