---
title: "Transfer traces to a project"
method: POST
path: "/v1/traces/transfer"
tags: ["traces"]
---

# Transfer traces to a project

`POST /v1/traces/transfer`

Move traces into a different project. This re-parents the traces rather than copying them, so they no longer appear under their original project. All traces must currently belong to the same source project.

## Request body

- TransferTracesRequestBody
  - `trace_identifiers` string[], required — The traces to transfer. Each identifier is either a trace ID (GlobalID) or an OpenTelemetry trace_id (hex string). Must be non-empty, and all traces must currently belong to the same source project.
  - `destination_project_identifier` string, required — The destination project: either project ID (GlobalID) or project name.

## Response `200`

Successful Response

- TransferTracesResponseBody
  - `data` TransferTracesData, required
    - `transferred_trace_count` integer, required — The number of traces that were moved to the destination project.
    - `destination_project_id` string, required — The ID (GlobalID) of the project the traces were moved to.

## Other responses

- `403` — Forbidden
- `404` — Destination project or trace not found
- `422` — Invalid request

---

[API](https://skmtc.net/arize-ai/apis/arize-phoenix-rest-api.md) · [All operations](https://skmtc.net/arize-ai/apis/arize-phoenix-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/arize-ai/arize-phoenix-rest-api/revisions/279647a4fbc6/schema)