Loading ...

REST API: Get Event Resource | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Events » REST API: Event Resources » REST API: Get Event Resource
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 24

REST API: Get Event Resource

0 
 /5
0 (0votes)
Open API Guide
GET/api/events/resources/{ResourceID}

Enables administrators and developers to programmatically retrieve an event resource.

Request

Request Header

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

Required Parameters

ParameterTypeRequiredLocationDescription
ResourceIDIntegerYESPathUnique ID of the event resource

Example

Request Header

Authorization: Bearer YOUR_TOKEN

Request URL

https://your-site.com/api/events/resources/5

Success Response

{
  "IsError": false,
  "ResponseMessage": "",
  "ResponseData": {
    "ResourceID": 5,
    "ResourceName": "Conference Room A",
    "Location": "Office Building A",
    "Description": "Place for large meetings",
    "EventResourceTypeID": 1,
    "Type": {
      "EventResourceTypeID": 1,
      "ResourceKey": "RoomText",
      "IsRoom": true
    },
    "ImageFilename": "59eed55a-34fc-4337-a936-90f90d847d47.jpg",
    "SpaceIDCSV": "205,206,207",
    "DateCreated": "0001-01-01T00:00:00"
  }
}

Error Response

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

Error Handling

Status CodeLikely CauseNext Action
400 Bad RequestResourceID in the path is not an integer.Send the resource's numeric ID.
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.
200 with ResponseData nullNo event resource has that ID.Check the ResourceID.
500 Server ErrorInternal failure.Retry later.
200 with IsErrorResourceID is 0 or negative (Not a valid resourceID.).Send the resource's ID.

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