---
title: "List traffic allocations"
method: GET
path: "/traffic-allocations"
tags: ["Traffic Allocations"]
---

# List traffic allocations

`GET /traffic-allocations`

## Request

- Base URL: `https://api.vapi.ai`
- URL: `https://api.vapi.ai/traffic-allocations`
- Auth: HTTP bearer

The append-only history of an assistant's allocations, newest first.

## Query parameters

- `assistantId` string
- `page` integer
- `limit` integer
- `sortOrder` 'ASC' | 'DESC'

## Response `200`

- TrafficAllocationPaginatedResponse
  - `results` TrafficAllocation[], required
    - `id` string, required: Unique identifier. The most recently created allocation for an assistant is the one in effect.
    - `orgId` string, required
    - `assistantId` string: The assistant this allocation splits calls for.
    - `allocationIntent` 'follow-latest' | 'explicit', required: 'explicit' splits calls across this allocation's targets. 'follow-latest' sends every call to the newest published version.
    - `createdAt` string, date-time, required: When this allocation was created, which is also when it took effect.
    - `actorType` 'user' | 'api-key' | 'system', required: Who created this allocation. 'system' means Vapi created it automatically, for example when a publish advances a follow-latest allocation.
    - `actorId` string: The user id or API key id that created this allocation. Absent for system rows.
    - `actorEmail` string: Email of the user who created this allocation, as of that time.
    - `description` string: The note given when this allocation was created, if any.
    - `targets` TrafficAllocationTarget[], required: The versions this allocation splits calls across, in position order. Empty for follow-latest allocations.
      - `assistantVersion` string, required: The assistant version this target sends calls to, such as "v7".
      - `position` number, required: The target's place in the split, starting at 0. Set from the order of the targets array.
      - `percentage` number, required: Share of calls sent to this version, from 0 to 100 with up to three decimal places. Targets add up to exactly 100. A 0% target keeps the version in the split without sending it calls.
  - `metadata` PaginationMeta, required
    - `itemsPerPage` number, required
    - `totalItems` number, required
    - `currentPage` number, required
    - `totalPages` number
    - `hasNextPage` boolean
    - `nextCursor` string: Opaque cursor for the next page under keyset pagination (PRO-3163). Pass it back as the `cursor` query param to fetch the next page without an OFFSET scan. Present only when a further page likely exists.
    - `sortOrder` 'ASC' | 'DESC'
    - `itemsBeyondRetention` boolean
    - `createdAtLe` string, date-time
    - `createdAtGe` string, date-time

## Other responses

- `403`: Traffic splitting is not enabled for your organization. The feature is in beta, rolling out to select organizations.

## Changes

> 164 revisions in range; 15 not diffed, 8 could not be searched.

- **2026-10-01** `e32916789bb1`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/vapiai/apis/vapi-api/changes/traffic-allocations/get.md)

---

[API](https://skmtc.dev/vapiai/apis/vapi-api.md) - [All operations](https://skmtc.dev/vapiai/apis/vapi-api/llms.txt) - [OpenAPI document](https://skmtc.dev/vapiai/apis/vapi-api/revisions/d73a715574fb?raw)