Show source

Personalization

Personalization is the process of adding a name and other consumer details to one or more tickets. Personalizing a ticket is only possible in the personalization period of an event. You can get the personalization period from the Event resource.

Some events require that tickets are personalized before allowing entry. Usually this means you have to personalize all tickets in an order before the E-Ticket download option becomes available.

After successfully personalizing a ticket, the fan will receive an email confirming the personalization.

There are two ways to do the personalization request:

Personalize a ticket as the order creator

Use this way when you have access to the order. You have access to the order if you own an Order token or when you have a Cognito token for the creator of the order.

Request data

Field name Type Description
order Orders reference A reference to the order of the tickets.
tickets Ticket references A list of tickets references to be personalized.
consumer Consumer A consumer object, describing the information of the consumer for whom the order is being placed.
opt_in Object with {<opt_in>: <Boolean>} Opt-in choice indicating teh consumer’s preference regarding newsletters and marketing. See Setting a consumer’s opt-in preferences.

Example request

# With an Order-Token or Cognito-Token request header
[POST] https://shopping-api.paylogic.com/personalization

{
  "order": "https://shopping-api.paylogic.com/orders/1a701ca300944a0da88212b5c18e74d2&q",
  "tickets": [
    "https://shopping-api.paylogic.com/tickets/333cdbb9ce254c7e9fb4c10337481d04"
  ],
  "consumer": {
    "gender": 1,
    "first_name": "John",
    "last_name": "Doe",
    "date_of_birth": "1970-01-01",
    "email": "john.doe@example.org"
  },
  "opt_in": {
    "opt_in": false,
    "opt_in_2": false
  }
}

The server will respond with 204 NO CONTENT if the ticket was successfully personalized.

Personalize a ticket as a friend

Use this way when someone other than the creator of an order needs to personalize a ticket. This flow is explained in Personalization Requests. Authenticate the request with a Personalization request token.

Request data

Field name Type Description
personalization_request Personalization Requests reference A reference to the personalization_request of the tickets.
tickets Ticket references A list of references to tickets that should be personalized.
consumer Consumer A consumer object, describing the information of the consumer for whom the order is being placed.
opt_in Object with {<opt_in>: <Boolean>} Opt-in choice indicating teh consumer’s preference regarding newsletters and marketing. See Setting a consumer’s opt-in preferences.

Example request

# With a Personalization-Request-Token request header
[POST] https://shopping-api.paylogic.com/personalization

{
  "personalization_request": "https://shopping-api.paylogic.com/personalization-requests/cbc0fde8aa804984b559feab6d8fc683",
  "tickets": [
    "https://shopping-api.paylogic.com/tickets/333cdbb9ce254c7e9fb4c10337481d04"
  ],
  "consumer": {
    "gender": 1,
    "first_name": "John",
    "last_name": "Doe",
    "date_of_birth": "1970-01-01",
    "email": "john.doe@example.org"
  },
  "opt_in": {
    "opt_in": false,
    "opt_in_2": false
  }
}

The server will respond with 204 NO CONTENT if the ticket was successfully personalized.

Personalization Requests Orders