---
title: "Screen"
method: POST
path: "/v1/screen"
tags: ["HTTP API"]
---

# Screen

`POST /v1/screen`

The screen call is the mobile equivalent of the page call. It lets you record whenever your user views their mobile screen with any additional relevant information about the screen.

## Request body

- ScreenPayload
  - `userId` string — Unique identifier for a particular user in your database.
  - `anonymousId` string — Sets the user ID for cases where there is no unique identifier for the user.
  - `name` string — Name of the screen being viewed.
  - `properties` object — Dictionary of the properties associated with the page being viewed, such as url and referrer.
  - `context` object — Dictionary of information that provides context about a message.
    - `ip` string — IP address.
    - `library` object
      - `name` string — Name of the library.
  - `timestamp` string, date-time — The timestamp of the message’s arrival.

## Response `200`

StatusOK

## Other responses

- `400` — StatusBadRequest
- `401` — StatusUnauthorized
- `404` — StatusNotFound
- `413` — StatusRequestEntityTooLarge
- `429` — StatusTooManyRequests

---

[API](https://skmtc.dev/rudderlabs/apis/rudderstack-http-api.md) · [All operations](https://skmtc.dev/rudderlabs/apis/rudderstack-http-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/rudderlabs/rudderstack-http-api/revisions/51895af9035c/schema)