---
title: "REST API: Get Event Resource Availability"
type: "wiki"
space: "Axero Documentation"
author: "Anonymous User"
created: 2020-07-08T23:24:10Z
updated: 2026-10-02T12:56:01Z
tags: ["API"]
url: "https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/42880/rest-api-get-event-resource-availability"
---

# REST API: Get Event Resource Availability

[Open API Guide](https://my.axerosolutions.com/spaces/5/axero-documentation/api-guide?id=42880)
GET/api/events/resources/availability

Check whether an event resource is free for a period of time. ResponseData is true when the resource is free and false when another event has booked it during that period.

## Request

### Request Header
| Header | Required | Value | Description |
| :--- | :--- | :--- | :--- |
| `Authorization` | YES | `Bearer YOUR_TOKEN` | Bearer token for the authenticated user. [Learn how to create Bearer tokens](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/108973/creating-bearer-tokens). |
### Required Parameters
| Parameter | Type | Required | Location | Description |
| :--- | :--- | :--- | :--- | :--- |
| `ResourceID` | Integer | YES | Query | Unique ID of the event resource to check availability of. An ID that matches no resource is not refused: ResponseData is true. |
| `StartDateTimeISO` | String | YES | Query | Start of the period to check, as an ISO 8601 date and time in the calling user's time zone, such as 2026-01-01T12:00:00. Leave off the Z and any offset. A trailing Z is ignored, so the time is still read in the calling user's time zone, and a value with an offset such as -06:00 is read as the wrong time. Without it, the call returns the resource's details instead of an availability result. |
| `EndDateTimeISO` | String | YES | Query | End of the period to check, in the same form as StartDateTimeISO. Without it, the call returns the resource's details instead of an availability result. |
### Optional Parameters
| Parameter | Type | Required | Location | Description |
| :--- | :--- | :--- | :--- | :--- |
| `EventID` | Integer | NO | Query | ID of an existing event to leave out of the check, so that event's own booking does not count as a conflict. A value that is not a whole number is ignored. |
## Example

### Request Header

```
Authorization: Bearer YOUR_TOKEN
```

### Request URL

`https://your-site.com/api/events/resources/availability?resourceID=14&startDateTimeISO=2026-01-01T12:00:00&endDateTimeISO=2026-02-01T00:00:00`

### Success Response

```
{
  "IsError": false,
  "ResponseMessage": "",
  "ResponseData": true
}
```

### Error Response

```
{
  "Message": "The request is invalid."
}
```

## Error Handling

| Status Code | Likely Cause | Next Action |
| :--- | :--- | :--- |
| 400 Bad Request | ResourceID is missing or not an integer. | Send ResourceID. |
| 401 Unauthorized | Missing or invalid Bearer token. | Check token validity. [Learn how to create Bearer tokens →](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/108973/creating-bearer-tokens) |
| 403 Forbidden | Not returned: the endpoint has no check that answers 403. | Check the ResourceID and dates if the result looks wrong. |
| 500 Server Error | StartDateTimeISO or EndDateTimeISO is not a date, or is sent with no value. The body is empty. | Send both dates in ISO 8601 form. |
| 200 with resource details | StartDateTimeISO or EndDateTimeISO is missing; IsError stays false and ResponseData carries the resource's details instead of an availability result. When no resource has that ID, ResponseMessage reads Content not found. and there is no ResponseData. | Send both dates in ISO 8601 form. |

## 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.