Using tags and tracks you can label sessions and group them according to your convenience. It helps to filter out sessions based on tags and tracks.
To create tags or tracks for an event same API endpoints are used. They are differentiated by
type field. For tags and tracks
type fields' values should be
name are required fields, apart from them you can also pass additional fields like
This API can be used by authenticated users only and it will require super admin/admin/staff level access.
Here is the description of response attributes, which returns to the form of JSON.
|ID||Unique tag or tracks ID.|
Here is the possible error messages, which return if any condition gets failed or required data is missing for processing.
|Error Code||Error Description|
|400||The request could not be understood by the server due to malformed syntax.|
|401||You are not authorized to view the resource.|
|403||Accessing the resource you were trying to reach is forbidden.|
|404||The resource you were trying to reach is not found.|