# Initiating a transfer

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.

Endpoint: POST /transfers
Version: 3.0.0
Security: SessionKey

## Request fields (application/json):

  - `sender` (string)
    Unique identifier of the account initiating this transfer

  - `recipient` (string)
    Account identifier of the transfer recipient

  - `tickets` (object)
    Sections for which to transfer tickets. The object's keys are the URI of the event section of the tickets being transferred, while its values are the number of tickets to transfer for that section.

## Response 201 fields (application/json):

  - `self` (string)
    URI of the transfer resource

  - `status` (string)
    Current status of the transfer

  - `initiated` (string)
    The date and time at which the transfer was initiated

  - `sender` (object)

  - `sender.self` (string)
    URI of the account resource

  - `sender.number` (string)
    Immutable identifier attached to the account

  - `sender.username` (string)
    Unique username attached to the account

  - `sender.email` (string)
    Unique email address attached to the account

  - `sender.firstName` (string)
    The account holder's forename

  - `sender.lastName` (string)
    The account holder's surname

  - `recipient` (object)

  - `tickets` (array)
    List of tickets involved in the transfer

  - `tickets.name` (string)
    The event section of the ticket being transferred

  - `tickets.description` (string)
    Detailed description of the transferred ticket

  - `tickets.quantity` (number)
    Number of tickets for this section being transferred

  - `claims` (string)
    URI for the claims collection used to complete the transfer

## Response 400 fields (application/json):

  - `message` (string)
    Reason for the given response.

## Response 403 fields (application/json):

  - `message` (string)
    Reason for the given response.

## Response 404 fields (application/json):

  - `message` (string)
    Reason for the given response.

## Response 409 fields (application/json):

  - `message` (string)
    Reason for the given response.