Users
In order to access private user data, you will need to include authentication tokens in your API request. See our authentication guide for notes on each of our supported authentication schemes.
Eventbrite attendees can review their past ticket history via the user_list_tickets call.
Event organizers can automate tasks and review or reuse previously created content from past events, venues, and organizer profiles.
Related Methods
Object Structure
| Name | description |
|---|---|
| user_id | The User ID. |
| The user email address. | |
| first_name | The first name of the user. |
| last_name | The last name of the user. |
| user_key | API user key. A non-revokable access token, which should be stored in place of an email and password combo. This field is not included in OAuth2.0 access_token-based API requests. |
| date_created | The date and time the user was created, in ISO 8601 format (e.g., “2007-12-31 23:59:59″). |
| date_modified | The date and time the user was last modified, in ISO 8601 format (e.g., “2007-12-31 23:59:59″). |
| subusers | An array of ‘subuser’ objects that may have been granted access to this account. Object attributes include: id, email |