---
title: "REST API: Create Event Type"
type: "wiki"
space: "Axero Documentation"
author: "Anonymous User"
created: 2011-03-29T06:00:28Z
updated: 2026-09-28T01:09:36Z
tags: ["API"]
url: "https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/504/rest-api-create-event-type"
---

# REST API: Create Event Type

[Open API Guide](https://my.axerosolutions.com/spaces/5/axero-documentation/api-guide?id=504)
POST/api/eventtypes

Create an event type, or update an existing one when EventTypeID is sent.

## 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 |
| :--- | :--- | :--- | :--- | :--- |
| `Event Type JSON` | String | YES | Body | The event type you're creating, as a JSON object shaped like the Request Body example below. Its fields are the rows that follow. |
| `EventTypeName` | String | YES | Body | Name of the event type |
| `SpaceID` | Integer | YES | Body | Unique ID of the space. Without it, or with a value that is not a number, SpaceID is 0 and the type is created at the site level; the endpoint still answers 200 and reports no error. |
### Optional Parameters
| Parameter | Type | Required | Location | Description |
| :--- | :--- | :--- | :--- | :--- |
| `EventTypeID` | Integer | NO | Body | ID of an existing event type to update instead of creating a new one, sent in the request body. Omit to create. A value that is not a number is read as 0, and a new type is created. |
## Example

### Request Header

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

### Request URL

`https://your-site.com/api/eventtypes`

### Request Body

```
{
  "EventTypeName": "Meeting",
  "SpaceID": 0
}
```

### Success Response

```
{
  "IsError": false,
  "ResponseMessage": "True",
  "ResponseData": 1014
}
```

### Error Response

```
HTTP 500 with an empty body
```

## Error Handling

| Status Code | Likely Cause | Next Action |
| :--- | :--- | :--- |
| 500 Server Error | A required parameter is missing. A request with no body fails with 500 instead of reporting the missing value. | Verify the request against the required parameters before treating the 500 as a server fault. |
| 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. |
| 200 with IsError | An event type with that name already exists \(Event type already exists\). | Use a different EventTypeName. |

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