---
title: "REST API: Add Users to an Event As Attendees"
type: "wiki"
space: "Axero Documentation"
author: "Adam Ilowite"
created: 2022-12-20T15:39:51Z
updated: 2026-02-23T03:18:42Z
url: "https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/92910/rest-api-add-users-to-an-event-as-attendees"
---

# REST API: Add Users to an Event As Attendees

[Open API Guide](https://my.axerosolutions.com/spaces/5/axero-documentation/api-guide?id=92910)
POST/api/events/\{EventID\}/users

Add individual users to an event as invitees or attendees

## 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 |
| `IsCommunityUser` | Boolean | YES | Body | Set to true if the user you are adding to the event is a registered user on the site.<br>Set to false if the user you are adding to the event is not a registered user |
| `UserID` | Integer | YES | Body | User ID of the user you are adding to the event |
| `AttendanceType` | Integer | YES | Body | 1: Attending<br>2: Maybe attending<br>3: Not attending |
## Example

### Request Header

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

### Request URL

`https://your-site.com/api/events/670/users`

### Request Body

```
[{"IsCommunityUser":true,"UserID":"614","AttendanceType":1}]
```

### Success Response

```
{
  "IsError": false,
  "ResponseMessage": "The request was processed successfully.",
  "ResponseData": true
}
```

### Error Response

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

## Error Handling

| Status Code | Likely Cause | Next Action |
| :--- | :--- | :--- |
| 400 Bad Request | One or more required fields are missing or invalid. \(eventID, users\) | Verify the request payload against the required parameters. |
| 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. |
| 404 Not Found | The specified event was not found. | Verify the eventID is correct. |
| 500 Server Error | Internal 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.