Loading ...

REST API: Get Event Type | Axero Documentation

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

REST API: Get Event Type

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

Enables administrators and developers to programmatically retrieves event type information.

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens.

Required Parameters

ParameterTypeRequiredLocationDescription
EventTypeIDIntegerYESPathUnique identifier for a particular event type

Example

Request Header

Authorization: Bearer YOUR_TOKEN

Request URL

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

Success Response

{
  "IsError": false,
  "ResponseMessage": "",
  "ResponseData": {
    "EventTypeID": 871,
    "EventTypeName": "API Validate matrix type 55b6",
    "SpaceID": 313,
    "SpaceName": "API Validate Sandbox",
    "TenantID": 1
  }
}

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.Send the event type's numeric ID.
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 ResponseData nullNo event type has that ID.Check the EventTypeID.
500 Server ErrorInternal failure.Retry later.
200 with IsErrorEventTypeID is 0 or negative (Not a valid eventTypeID.).Send the event type's ID.

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