---
title: "Batch"
method: POST
path: "/v1/batch"
tags: ["HTTP API"]
---

# Batch

`POST /v1/batch`

The batch call enables you to send a batch of events (identify, track, page, group, screen, alias) in a single request.

## Request body

- BatchPayload
  - `batch` object[], required
    - `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.
    - `context` object — Dictionary of information that provides context about a message.
      - `traits` object
        - `trait1` string — New value for trait1.
      - `ip` string — IP address.
      - `library` object
        - `name` string — Name of the library.
    - `timestamp` string, date-time — The timestamp of the message’s arrival.
    - `event` string — Name of the event being performed by the user.
    - `properties` object — Dictionary of the properties associated with the page being viewed, such as url and referrer.
    - `name` string — Name of the screen being viewed.
    - `groupId` string — Unique identifier of the group, as present in your database.
    - `traits` object — Dictionary of the traits associated with the group, such as name or email.
    - `previousId` string — The previous unique identifier of the user.
    - `type` string

## 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)