---
title: "REST API: Mark As Organizer"
type: "wiki"
space: "Axero Documentation"
author: "Anonymous User"
created: 2020-07-08T18:32:52Z
updated: 2026-09-28T01:18:33Z
tags: ["API"]
url: "https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/42868/rest-api-mark-as-organizer"
---

# REST API: Mark As Organizer

[Open API Guide](https://my.axerosolutions.com/spaces/5/axero-documentation/api-guide?id=42868)
PUT/api/events/\{EventID\}/organizer

Mark or unmark an event invitee or attendee as an organizer. The response is the bare value true, not the response envelope.

## 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 |
| `UserID` | Integer | YES | Query | Unique ID of the user to mark as event organizer. The call returns True even for a user who is not an invitee or attendee, and that user is not added to the invitees or attendees. |
### Optional Parameters
| Parameter | Type | Required | Location | Description |
| :--- | :--- | :--- | :--- | :--- |
| `IsOrganizer` | Boolean | NO | Query | Whether to set the user as an organizer or not. True by default. |
| `IsCommunityUser` | Boolean | NO | Query | true \(default\) when the user is a site member; false when the user is a guest attendee. |
## Example

### Request Header

```
Authorization: Bearer YOUR_TOKEN
Content-Type: application/json
```

### Request URL

`https://your-site.com/api/events/183/organizer?UserID=1018&IsOrganizer=true`

### Success Response

```
true
```

### Error Response

```
{
  "Message": "No HTTP resource was found that matches the request URI 'https://your-site.com/api/events/1730/organizer'."
}
```

## Error Handling

| Status Code | Likely Cause | Next Action |
| :--- | :--- | :--- |
| 400 Bad Request | EventID in the path or UserID is not an integer, or IsOrganizer is not a boolean. | Check the values. |
| 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. |
| 404 or 405 | A required query parameter was left out, so the request matched a different action or none. The message reads No HTTP resource was found or The requested resource does not support http method. | Send every required query parameter. The message does not mean the item you asked for is missing. |

## 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.
