Loading ...

REST API: Create Event Type | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Content » REST API: Events » REST API: Event Types » REST API: Create Event Type
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 35

REST API: Create Event Type

0 
 /5
0 (0votes)
Open API Guide
POST/api/eventtypes

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

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens.
Content-TypeYESapplication/jsonMust be set to application/json

Required Parameters

ParameterTypeRequiredLocationDescription
Event Type JSONStringYESBodyThis is JSON that represents an event type object that you're creating. This should be of the format seen below in the sample given. The required values in this JSON are given below.
EventTypeNameStringYESBodyName of the event type
SpaceIDIntegerYESBodyUnique ID of space. Not validated by the endpoint: a request without it answers 200, so a missing value is not reported as an error.

Optional Parameters

ParameterTypeRequiredLocationDescription
EventTypeIDIntegerNOQueryID of an existing event type to update instead of creating a new one. Omit to create.

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": 872
}

Error Response

HTTP 500 with an empty body

Error Handling

Status CodeLikely CauseNext Action
500 Server ErrorA required parameter is missing. The endpoint fails with an empty body instead of reporting the missing value.Verify the request against the required parameters before treating the 500 as a server fault.
401 UnauthorizedMissing or invalid Bearer token.Check token validity. Learn how to create Bearer tokens →
403 ForbiddenUser does not have sufficient permissions.Confirm the user has the required roles for this action.
200 with IsErrorAn 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.

Wiki Index

Pages