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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Fresnel Software

Fresnel Software Ticketing API

The Ticketing API from Fresnel Software — 9 operation(s) for ticketing.

Documentation Provider Profile APIs.io OpenAPI GitHub

Fresnel Software Ticketing API is one of 70 APIs that Fresnel Software 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.

This API exposes 17 operations across 9 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://{workspace}.api.vitruvi.cc.

17 operations 9 paths 19 schemas 2 DELETE9 GET2 PATCH2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
https://{workspace}.api.vitruvi.cc
Authentication
HTTP Basic, API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 3

Fresnel Software Ticketing API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as Authorization (jwtAuth). It accepts HTTP bearer tokens (tokenAuth).

  • jwtAuth — Token-based authentication with required prefix "JWT"

Paths & Operations 17

Across 9 paths, the API surfaces 17 operations — 2 DELETE, 9 GET, 2 PATCH, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Ticketing 17
GET
/api/v1/ticketing/custom_field_visibility/
List Ticket Custom Field Visibilities
list_ticketing_custom_field_visibility 5 params → 200
POST
/api/v1/ticketing/custom_field_visibility/
Create Ticket Custom Field Visibility
create_ticketing_custom_field_visibility body → 201
GET
/api/v1/ticketing/custom_field_visibility/{id}/
Retrieve Ticket Custom Field Visibility
get_ticketing_custom_field_visibility 1 param → 200
PUT
/api/v1/ticketing/custom_field_visibility/{id}/
Update Ticket Custom Field Visibility
update_ticketing_custom_field_visibility 1 param body → 200
PATCH
/api/v1/ticketing/custom_field_visibility/{id}/
Partial Update Ticket Custom Field Visibility
patch_ticketing_custom_field_visibility 1 param body → 200
DELETE
/api/v1/ticketing/custom_field_visibility/{id}/
Delete Ticket Custom Field Visibility
delete_ticketing_custom_field_visibility 1 param → 204
GET
/api/v1/ticketing/ticket_actions/
List Ticket Actions
list_ticketing_ticket_actions 6 params → 200
GET
/api/v1/ticketing/ticket_actions/{id}/
Retrieve Ticket Action
get_ticketing_ticket_actions 1 param → 200
GET
/api/v1/ticketing/ticket_collections/
List Ticket Collections
list_ticketing_ticket_collections 9 params → 200
GET
/api/v1/ticketing/tickets/
List Tickets
list_ticketing_tickets 17 params → 200
POST
/api/v1/ticketing/tickets/
Create Ticket
create_ticketing_tickets body → 201
GET
/api/v1/ticketing/tickets/{id}/
Retrieve Ticket
get_ticketing_tickets 1 param → 200
PUT
/api/v1/ticketing/tickets/{id}/
Update Ticket
update_ticketing_tickets 1 param body → 200
PATCH
/api/v1/ticketing/tickets/{id}/
Partial Update Ticket
patch_ticketing_tickets 1 param body → 200
DELETE
/api/v1/ticketing/tickets/{id}/
Delete Ticket
delete_ticketing_tickets 1 param → 204
GET
/api/v1/ticketing/tickets/{id}/download_attachment/
Download Attachment (Ticket)
api_v1_ticketing_tickets_download_attachment_retrieve 1 param → 200
GET
/api/v1/ticketing/tickets_query
Tickets Grid View
tickets_query → 200

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are PatchedTicket (44 properties), Ticket (44 properties), TicketCollection (14 properties), TicketAttachment (9 properties). Each schema is shown below with its type and property counts.

GlobalStatusEnum
string
open - open closed - closed completed - completed
PaginatedTicketActionList
object
4 properties
TicketCustomFieldVisibility
object
7 properties 4 required
NullEnum
GlobalPriorityEnum
integer
10 - Low 20 - Medium 30 - High 40 - Critical
PaginatedTicketCollectionList
object
4 properties
Status8a1Enum
string
open - open closed - closed completed - completed
TicketAttachment
object
9 properties 6 required
TicketCollection
object
14 properties 9 required
TicketAction
object
9 properties 8 required
Ticket
object
44 properties 28 required
PatchedTicket
object
44 properties
TicketComment
object
8 properties 5 required
PaginatedTicketCustomFieldVisibilityList
object
4 properties
PatchedTicketCustomFieldVisibility
object
7 properties
TicketActionChange
object
8 properties 7 required
PriorityEnum
integer
10 - Low 20 - Medium 30 - High 40 - Critical
VisibilityOnMobileAppEnum
string
hidden - hidden view only - view only editable - editable
PaginatedTicketList
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vitruvi-ticketing-api-openapi.yml Raw ↑

Other APIs Fresnel Software publishes across the network.

Vitruvi Platform
AE Profile APIs.io
Fresnel Software Aggregation API
AE Profile APIs.io
Fresnel Software Ai agent API
AE Profile APIs.io
Fresnel Software Async events API
AE Profile APIs.io
Fresnel Software Auth API
AE Profile APIs.io
Fresnel Software Conditional custom field overrides API
AE Profile APIs.io
Fresnel Software Configuration library API
AE Profile APIs.io
Fresnel Software Content types API
AE Profile APIs.io
Fresnel Software Crew categories API
AE Profile APIs.io
Fresnel Software Crews API
AE Profile APIs.io
Fresnel Software Crews with resources API
AE Profile APIs.io
Fresnel Software Custom field categories API
AE Profile APIs.io
#Ticketing
← Back to F APIs
API Details
ID
vitruvi:vitruvi-ticketing-api
Server
https://{workspace}.api.vitruvi.cc
Docs
https://vitruvisoftware.com/platform/overview
Provider
Fresnel Software
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=vitruvi-ticketing-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/vitruvi-ticketing-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Fresnel Software 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.