Loading ...

REST API: Get User RSVP | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Events » REST API: Get User RSVP
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 23

REST API: Get User RSVP

0 
 /5
0 (0votes)
Open API Guide
GET/api/events/{EventID}/rsvp/{UserID}/status

Enables administrators and developers to programmatically retrieve a user's RSVP for a particular event. The response is the bare attendance value (1 = Attending, 2 = Maybe attending, 3 = Not attending, 5 = Awaiting response), not the response envelope.

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

Optional Parameters

ParameterTypeRequiredLocationDescription
IsCommunityUserBooleanNOQuerytrue when UserID is a site member. Send false to look up the RSVP of an external invitee. Defaults to true.

Example

Request Header

Authorization: Bearer YOUR_TOKEN

Request URL

https://your-site.com/api/events/183/rsvp/1017/status

Success Response

1

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