How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Velaris Ticketing API

The Ticketing API from Velaris — 6 operation(s) for ticketing.

Velaris Ticketing API is one of 14 APIs that Velaris publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Ticketing. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 12 operations across 6 paths. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against a single base URL, https://api.euw1.velaris.io.

12 operations 6 paths 0 schemas 2 DELETE5 GET2 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://api.euw1.velaris.io
Authentication
HTTP Bearer, HTTP Basic
Contact
Resource Areas
1

Authentication & Security 2

Velaris Ticketing API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • bearerAuth — User-scoped access token. Header: Authorization: Bearer {accesstoken}. Create under Profile Security Access token.
  • basicAuth — Legacy. Base64(username:password). Not available for SSO/MFA tenants.

Paths & Operations 12

Across 6 paths, the API surfaces 12 operations — 2 DELETE, 5 GET, 2 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Ticketing 12
GET
/ticketing/tickets
Get All Tickets
getAllTickets → 200
POST
/ticketing/tickets
Create Ticket
createTicket body → 200
GET
/ticketing/tickets/:ticketId
Get Ticket By Id
getTicketById → 200
PUT
/ticketing/tickets/:ticketId
Update Ticket
updateTicket body → 200
DELETE
/ticketing/tickets/:ticketId
Delete Ticket
deleteTicket → 200
PUT
/ticketing/tickets/:ticketId/restore
Restore Ticket
restoreTicket → 200
GET
/ticketing/tickets/:ticketId/comments
Get All Comments
getAllComments → 200
POST
/ticketing/tickets/:ticketId/comments
Create Comment
createComment body → 200
GET
/ticketing/tickets/:ticketId/comments/:commentId
Get Comment By Id
getCommentById → 200
PUT
/ticketing/tickets/:ticketId/comments/:commentId
Update Comment
updateComment body → 200
DELETE
/ticketing/tickets/:ticketId/comments/:commentId
Delete Comment
deleteComment → 200
GET
/ticketing/tickets/:ticketId/comments/external/:externalId
Get Comment by External ID
getCommentByExternalId → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

velaris-ticketing-api-openapi.yml Raw ↑

Other APIs Velaris publishes across the network.

Velaris Activity API
Velaris Attribute Change Log API
Velaris Currencies API
Velaris Custom Objects API
Velaris Entity Management V1 API
Velaris Entity Management V2 API
Velaris Field Definitions API
Velaris Integrations API
Velaris Lifecycles API
Velaris Notes API
Velaris Surveys API
Velaris Tasks API
Where this information came from

This is an independent, third-party profile of Velaris Ticketing API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.