---
title: "REST API: Update RSVP"
type: "wiki"
space: "Axero Documentation"
author: "Anonymous User"
created: 2020-07-08T18:56:09Z
updated: 2026-09-28T01:21:26Z
tags: ["API"]
url: "https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/42869/rest-api-update-rsvp"
---

# REST API: Update RSVP

[Open API Guide](https://my.axerosolutions.com/spaces/5/axero-documentation/api-guide?id=42869)
PUT/api/events/\{EventID\}/rsvp/me/status

Set the calling user's RSVP for an event, or for one instance of a recurring event. ResponseData is the attendance value that was set.

## 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). |
| `Content-Type` | YES | `application/json` | Must be set to `application/json` |
### Required Parameters
| Parameter | Type | Required | Location | Description |
| :--- | :--- | :--- | :--- | :--- |
| `EventID` | Integer | YES | Path | Unique ID of the event |
| `RSVPStatus` | Integer | YES | Body | Attendance status to set: 1 Attending, 2 Maybe attending, 3 Not attending. Send the number on its own as the whole request body. Refer to [REST API: Event Attendance Types](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/25228/rest-api-event-attendance-types "REST API: Event Attendance Types"). |
### Optional Parameters
| Parameter | Type | Required | Location | Description |
| :--- | :--- | :--- | :--- | :--- |
| `InstanceOption` | Integer | NO | Query | For a recurring event, which instances the RSVP applies to: 1 All \(default\), 2 this and future instances, 3 a single instance. |
| `Instance` | String | NO | Query | The instance date the RSVP applies to when InstanceOption is 2 or 3. |
| `DeleteAttendUser` | Boolean | NO | Query | true also removes the caller from the event's attendee list when InstanceOption is 1. Default: false. |
## Example

### Request Header

```
Authorization: Bearer YOUR_TOKEN
Content-Type: application/json
```

### Request URL

`https://your-site.com/api/events/185/rsvp/me/status`

### Request Body

```
2
```

### Success Response

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

### Error Response

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

## Error Handling

| Status Code | Likely Cause | Next Action |
| :--- | :--- | :--- |
| 400 Bad Request | EventID in the path is not an integer, or the body is missing or not an attendance value. | Send a numeric EventID, and send the attendance value on its own as the body. |
| 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 | User does not have sufficient permissions. | Confirm the user has the required roles for this action. |
| 500 Server Error | Internal failure. | Retry later. |
| 200 with IsError | The event has reached its maximum number of attendees \(EventMaxAttendeesReached\). | Send 3 \(Not attending\), which is always accepted, or wait for a place. |

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