Loading ...

REST API: Update Event Type | Axero Documentation

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

REST API: Update Event Type

0 
 /5
0 (0votes)
Open API Guide
PUT/api/eventtypes/{EventTypeID}

Update an existing event type. ResponseMessage is the string True when the event type was saved and ResponseData is the EventTypeID.

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
EventTypeIDIntegerYESPathUnique identifier for a particular event type
EventType JSONStringYESBodyThis is JSON that represents an event type object that you're updating. This should be of the format seen below in the sample given.
EventTypeNameStringNOBodyName of the event type. Not enforced: the endpoint answers 200 without it.

Example

Request Header

Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

Request URL

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

Request Body

{
  "EventTypeName": "Meeting"
}

Success Response

{
  "IsError": false,
  "ResponseMessage": "True",
  "ResponseData": 871
}

Error Response

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

Error Handling

Status CodeLikely CauseNext Action
400 Bad RequestEventTypeID in the path is not an integer, or the body is not a JSON object.Send a numeric EventTypeID and a JSON object body.
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.
500 Server ErrorNo event type has that ID (the endpoint merges into the result without checking), or another internal failure.Check the EventTypeID, then 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.

Wiki Index

Pages