Loading ...

REST API: Delete User from Event | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Events » REST API: Delete User from Event
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 27

REST API: Delete User from Event

0 
 /5
0 (0votes)
Open API Guide
DELETE/api/events/{EventID}/users/members/{UserID}

Remove a user from an event's attendees or invitees.

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens.

Required Parameters

ParameterTypeRequiredLocationDescription
EventIDIntegerYESPathUnique ID of the event
UserIDIntegerYESPathUnique ID of the user to remove from the event

Optional Parameters

ParameterTypeRequiredLocationDescription
NotifyBooleanNOQueryWhether to send the user a cancellation notification. True by default.
InstanceOptionIntegerNOQueryFor a recurring event, which occurrences the removal applies to: 1 = All (default), 2 = Future, 3 = Single.
InstanceStringNOQueryFor a recurring event, the occurrence date the removal applies to when InstanceOption is 2 or 3. Default: none.

Example

Request Header

Authorization: Bearer YOUR_TOKEN

Request URL

https://your-site.com/api/events/130/users/members/1018?Notify=true

Success Response

true

Error Response

{
  "IsError": true,
  "ResponseMessage": "Required parameter is missing or invalid.",
  "ResponseData": null
}

Error Handling

Status CodeLikely CauseNext Action
400 Bad RequestEventID or UserID in the path is not an integer.Send numeric IDs in the path.
401 UnauthorizedMissing or invalid Bearer token.Check token validity. Learn how to create Bearer tokens →
403 ForbiddenUser does not have sufficient permissions.Confirm the user has the required roles for this action.
500 Server ErrorInternal failure.Retry later.

Rate Limits

While Axero does not enforce hard rate limits by default, we recommend the following best practices to ensure optimal performance:

  • Sustained Request Rate: Do not exceed 5 API calls per second
  • Sequential Processing: Wait for each request to complete before sending the next in automated workflows
  • Concurrent Connections: If parallel processing is required, limit to 3 or fewer simultaneous requests
  • Response Timeout: Ensure API responses complete within 15 seconds during testing

Axero may implement temporary rate restrictions if excessive API usage affects overall site performance. For high-volume integrations, contact Axero to discuss your requirements.

Wiki Index

Pages