Skip to main content

Event Users

The Event Users API allows you to create, retrieve, update, and delete users who can participate in events within your organization. These users can have different roles such as admin, organizer, or attendee.

Authentication

All requests to the Event Users API must be authenticated using the ONLIVE.SITE authentication scheme. Please refer to the Authentication Guide for detailed instructions.

Base URL

https://openapi.onlive.site/api/v1/event-users

Endpoints


Create Event User

Creates a new event user within your organization.

HTTP Request

POST /api/v1/event-users

Request Body

All fields are optional, but it's recommended to provide at least an email address or first/last name.

FieldTypeRequiredDescription
emailstring (email)NoThe email address of the user (max 255 characters)
firstNamestringNoThe first name of the user (max 255 characters)
lastNamestringNoThe last name of the user (max 255 characters)
phonestringNoThe phone number of the user (max 50 characters)
externalIdstringNoExternal identifier for the user from external systems (max 255 characters)
extraFieldsobjectNoAdditional fields for the user as a JSON object

Example Request Body

{
"email": "[email protected]",
"firstName": "John",
"lastName": "Doe",
"phone": "+1-555-123-4567",
"externalId": "ext_user_12345",
"extraFields": {
"department": "Engineering",
"role": "Developer",
"employeeId": "EMP-001"
}
}

Response

Returns the created EventUser object.

Example Response

{
"id": "123e4567-e89b-12d3-a456-426614174000",
"organizationId": "987e6543-e21a-34b5-c678-426614174000",
"email": "[email protected]",
"firstName": "John",
"lastName": "Doe",
"role": "attendee",
"avatar": null,
"isActive": true,
"createdAt": "2025-10-12T10:30:00.000Z",
"updatedAt": "2025-10-12T10:30:00.000Z"
}

Get Event User

Retrieves a specific event user by their ID.

HTTP Request

GET /api/v1/event-users/{id}

Path Parameters

ParameterTypeRequiredDescription
idstring (uuid)YesThe unique identifier of the event user

Query Parameters

ParameterTypeRequiredDescription
withTrashedbooleanNoInclude trashed users

Response

Returns the EventUser object.

Example Response

{
"id": "123e4567-e89b-12d3-a456-426614174000",
"organizationId": "987e6543-e21a-34b5-c678-426614174000",
"email": "[email protected]",
"firstName": "John",
"lastName": "Doe",
"role": "attendee",
"avatar": "https://example.com/avatars/user.jpg",
"isActive": true,
"createdAt": "2025-10-12T10:30:00.000Z",
"updatedAt": "2025-10-12T10:30:00.000Z"
}

Update Event User

Updates an existing event user.

HTTP Request

PUT /api/v1/event-users/{id}

Path Parameters

ParameterTypeRequiredDescription
idstring (uuid)YesThe unique identifier of the event user

Request Body

All fields are optional. Only the fields you want to update need to be included.

FieldTypeDescription
emailstring (email)The email address of the user (max 255 characters)
firstNamestringThe first name of the user (max 255 characters)
lastNamestringThe last name of the user (max 255 characters)
phonestringThe phone number of the user (max 50 characters)
externalIdstringExternal identifier for the user (max 255 characters)
extraFieldsobjectAdditional fields for the user as a JSON object

Example Request Body

{
"email": "[email protected]",
"phone": "+1-555-987-6543",
"extraFields": {
"department": "Product",
"role": "Senior Developer",
"employeeId": "EMP-001"
}
}

Response

Returns the updated EventUser object.


Search Event Users

Retrieves a paginated list of event users based on query parameters.

HTTP Request

GET /api/v1/event-users

Query Parameters

ParameterTypeRequiredDescription
limitnumberNoMaximum number of items to return (default: 10, min: 1)
pagenumberNoPage number (starts at 1, default: 1, min: 1)
sortstringNoField name and direction to sort results by. Use "ASC" or "DESC". (default: "createdAt DESC")
searchstringNoSearch term to filter users by name, ID, or external ID
withTrashedbooleanNoInclude soft-deleted users in the results

Example Request

GET /api/v1/event-users?search=John&role=attendee&isActive=true&page=1&limit=20

Response

Returns a paginated response with an array of EventUser objects.

Example Response

{
"data": [
{
"id": "123e4567-e89b-12d3-a456-426614174000",
"organizationId": "987e6543-e21a-34b5-c678-426614174000",
"email": "[email protected]",
"firstName": "John",
"lastName": "Doe",
"role": "attendee",
"avatar": "https://example.com/avatars/user.jpg",
"isActive": true,
"createdAt": "2025-10-12T10:30:00.000Z",
"updatedAt": "2025-10-12T10:30:00.000Z"
}
],
"meta": {
"total": 1,
"page": 1,
"limit": 20,
"totalPages": 1
}
}

Delete Event User

Deletes an event user by their ID.

HTTP Request

DELETE /api/v1/event-users/{id}

Path Parameters

ParameterTypeRequiredDescription
idstring (uuid)YesThe unique identifier of the event user

Query Parameters

ParameterTypeRequiredDescription
withTrashedbooleanNoInclude trashed users

Response

Returns the deleted EventUser object.


EventUser Object

The EventUser object represents a user who can participate in events.

Properties

PropertyTypeDescription
idstring (uuid)The unique identifier of the user
organizationIdstring (uuid)The organization identifier this user belongs to
emailstringThe email address of the user
firstNamestringThe first name of the user
lastNamestringThe last name of the user
rolestringThe role of the user. Possible values: admin, organizer, attendee
avatarstring | nullThe avatar URL of the user
isActivebooleanWhether the user is active (default: true)
organizationobjectThe organization associated with the event user
createdAtstring (ISO 8601)The date and time when the user was created
updatedAtstring (ISO 8601)The date and time when the user was last updated
deletedAtstring (ISO 8601)The deletion date of the user (if deleted)

User Roles

Event users can have one of the following roles:

  • admin: Full access to manage events, users, and organization settings
  • organizer: Can create and manage events, view registrations
  • attendee: Can register for events and view their own registrations

Notes

  • Event users are scoped to your organization and cannot be shared across organizations
  • The externalId field is useful for integrating with external systems and maintaining references to users in other platforms
  • Use the extraFields object to store custom data that doesn't fit into the standard user fields