---
title: "Get registration details for an event."
method: GET
path: "/events/{event_id}/tracks/{track_id}/registrations/{registration_id}"
tags: ["Events"]
---

# Get registration details for an event.

`GET /events/{event_id}/tracks/{track_id}/registrations/{registration_id}`

## Request

- Base URL: `https://api.cc.email/v3`
- URL: `https://api.cc.email/v3/events/{event_id}/tracks/{track_id}/registrations/{registration_id}`
- Auth: one of:
  - OAuth 2
    - Implicit: `https://authz.constantcontact.com/oauth2/default/v1/authorize`
    - Scopes: `campaign_data`
  - OAuth 2
    - Authorization code: `https://authz.constantcontact.com/oauth2/default/v1/authorize`
    - Token URL: `https://authz.constantcontact.com/oauth2/default/v1/token` scopes: `campaign_data`

Use the `event_id`, `registration_id`, and `track_id` path parameters to get registration details.

## Path parameters

- `event_id` string, required
- `track_id` string, required
- `registration_id` string, required

## Response `200`

Request Successful

- DetailedRegistrationDto
  - `registration_id` string: The unique ID used to identify an event registration.
  - `contact_id` string: The unique ID used to identify a contact.
  - `checkedIn_tickets` integer: The total number of tickets assigned to a given <code>registration_id</code>.
  - `checkin_status` string: Provides the status of eligible checkin tickets.
  - `eligible_checkin_tickets` integer: The total number of tickets eligible for checkin.
  - `registration_date` string, date-time: The event registration date, in ISO format.
  - `registration_status` string: Provides the current registration status; <code>REGISTERED</code>, <code>PENDING</code>, <code>CANCELED</code>, <code>EXPIRED</code>, <code>IN_PROGRESS</code>, <code>FAILED</code>.
  - `display_physical_tickets` boolean: Determines if the physical tickets should display or not display.
  - `contact` SimpleFieldDto[]
    - `display_order` integer: If specified, determines the order in which to return a subset of contact's details. For example, if you want a contact's email address to display first, set the <code>display_order</code> to <code>1</code> within the <code>field_label</code>: <code>CONTACT_EMAIL_ADDRESS</code> details section.
    - `field_label` string: The label used to identify a field within each contact details section.
    - `field_name` string: The formatted name used to identify a field within each contact details section.
    - `field_type` string: Identifies the type of field. Acceptable values include; TEXT_AREA, DATE, SINGLE_SELECT,MULTI_SELECT, INFORMATIONAL, TERMS_CONDITIONS, ADDRESS, HEADER, DIVIDER, STATIC_TEXT.
    - `label_key` string: The label used to identify a contact's registration details.
    - `field_value` string: The value of the field for this contact. For example, if the field is an email address, the field_value would contain the actual email address.
    - `choices` string[]: For SINGLE_SELECT and MULTI_SELECT field types, this array contains the available options the registrant can choose from.
  - `tickets` RegistrationTicketDto[]
    - `checked_in_time` string, date-time: The event check in time date, in ISO format.
    - `editable` boolean: Set to <code>true</code> to allow or <code>false</code> to not allow registrations to be modified.
    - `order_ticket_key` string: The system generated number used to identify a ticket order.
    - `price` number: The price for a ticket.
    - `ticket_name` string: The name used to identify the ticket.
    - `fields` SimpleFieldDto[]
      - `display_order` integer: If specified, determines the order in which to return a subset of contact's details. For example, if you want a contact's email address to display first, set the <code>display_order</code> to <code>1</code> within the <code>field_label</code>: <code>CONTACT_EMAIL_ADDRESS</code> details section.
      - `field_label` string: The label used to identify a field within each contact details section.
      - `field_name` string: The formatted name used to identify a field within each contact details section.
      - `field_type` string: Identifies the type of field. Acceptable values include; TEXT_AREA, DATE, SINGLE_SELECT,MULTI_SELECT, INFORMATIONAL, TERMS_CONDITIONS, ADDRESS, HEADER, DIVIDER, STATIC_TEXT.
      - `label_key` string: The label used to identify a contact's registration details.
      - `field_value` string: The value of the field for this contact. For example, if the field is an email address, the field_value would contain the actual email address.
      - `choices` string[]: For SINGLE_SELECT and MULTI_SELECT field types, this array contains the available options the registrant can choose from.
  - `order_summary` OrderDetailsDto
    - `details` LineItemDetailsDto[]
      - `amount` string: The formatted amount of the line item.
      - `amount_unformatted` number: The unformatted amount of the line item.
      - `line_item_type` string: Type of line item.
      - `name` string: The name of the line item.
    - `number` string: The system assigned string value used to identify the event order.
    - `payment_method` string: The payment method used when the order was placed. Acceptable payment methods include; `STRIPE` and `PAYPAL`.
    - `payment_status` string: The event registration payment status. Acceptable values include; <code>PENDING</code>, <code>PAID</code>, <code>REFUNDED</code>, <code>CANCELLED</code>, <code>FAILED</code>, <code>CHARGED_BACK</code>, <code>PENDING</code>, <code>UNKNOWN</code.
    - `payment_time` string: Displays the date and time the payment was made, in ISO format.
    - `payment_transaction_id` string: The unique ID used to identify a payment transaction.
    - `tickets_link` string: The URL used to access purchased tickets.
    - `tickets_text` string: Text that describes the event and ticket information.
    - `title` string: The title for the order.

## Other responses

- `400`: Bad request. Either the JSON was malformed or there was a data validation error.
- `401`: The Access Token used is invalid.
- `403`: Forbidden request. You lack the necessary scopes, you lack the necessary user privileges, or the application is deactivated.
- `404`: The requested resource was not found.
- `500`: There was a problem with our internal service.
- `503`: Our internal service is temporarily unavailable.

## Changes

- **2026-08-04** `4b4a534c818d`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/cc/apis/appconnect-v3/changes/events/:event_id/tracks/:track_id/registrations/:registration_id/get.md)

---

[API](https://skmtc.dev/cc/apis/appconnect-v3.md) - [All operations](https://skmtc.dev/cc/apis/appconnect-v3/llms.txt) - [OpenAPI document](https://skmtc.dev/cc/apis/appconnect-v3/revisions/7bcad1d0ff26?raw)
