# Ticket Transfers

## Initiating a transfer

 - [POST /transfers](https://docs.ticketingevents.com/openapi/ticket-transfers/initiate_transfer.md): Initiate a transfer of one or more tickets from the requesting user
to another TickeTing user. Initiating a transfer, does not automatically
move tickets between accounts, but instead sends a transfer request. This request
must first be claimed at which time the tickets themselves are transferred.
If the transfer request is cancelled or rejected, no tickets change hands.

One or more tickets, for one or multiple events, can be sent in a single transfer. 
Tickets that are part of an open transfer (not yet claimed, canclled or rejected)
enter into a pending state in which they cannot be redeemed, only becoming usable
again once a decision is taken on the transfer.

## Retrieve transfer details

 - [GET /transfers/{transfer}](https://docs.ticketingevents.com/openapi/ticket-transfers/retrieve_transfer.md): Retrieve the details of the requested transfer

## Cancel a transfer

 - [DELETE /transfers/{transfer}](https://docs.ticketingevents.com/openapi/ticket-transfers/cancel_transfer.md): Cancel a pending transfer. A transfer can be cancelled by either its sender or
its recipient before it is claimed. Any pending tickets attached to the transfer
are immediately released. A transfer can only be cancelled if it has not yet
been claimed, or previously cancelled.

## Claim a transfer

 - [POST /transfers/{transfer}/claims](https://docs.ticketingevents.com/openapi/ticket-transfers/claim_transfer.md): Claim a pending transfer. Once claimed, any tickets attached to the transfer are moved
from the sender's account to the recipient's and returned to a usable state. Only a
transfer's recipient can claim a transfer, and a transfer can no longer be claimed once
it has been cancelled or claimed previously.