Loading ...

REST API: Mark As Organizer | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Events » REST API: Mark As Organizer
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 24

REST API: Mark As Organizer

0 
 /5
0 (0votes)
Open API Guide
PUT/api/events/{EventID}/organizer

Mark or unmark an event invitee or attendee as an organizer. The response is the bare value true, not the response envelope.

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens.
Content-TypeYESapplication/jsonMust be set to application/json

Required Parameters

ParameterTypeRequiredLocationDescription
EventIDIntegerYESPathUnique ID of the event
UserIDIntegerYESQueryUnique ID of the user to mark as event organizer. The user must already be an event invitee or attendee.

Optional Parameters

ParameterTypeRequiredLocationDescription
IsOrganizerBooleanNOQueryWhether to set the user as an organizer or not. True by default.
IsCommunityUserBooleanNOQuerytrue (default) when the user is a site member; false when the user is a guest attendee.

Example

Request Header

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

Request URL

https://your-site.com/api/events/183/organizer?UserID=1018&IsOrganizer=true

Success Response

true

Error Response

{
  "Message": "No HTTP resource was found that matches the request URI 'https://your-site.com/api/events/1676/organizer'."
}

Error Handling

Status CodeLikely CauseNext Action
400 Bad RequestEventID in the path or UserID is not an integer, or IsOrganizer is not a boolean.Check the values.
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.
404 or 405A required query parameter was left out, so the request matched a different action or none: the message reads No HTTP resource was found or The requested resource does not support http method.Send every required query parameter; the message is not about the resource.

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