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

MINE Tickets API

The Tickets API from MINE — 16 operation(s) for tickets.

MINE Tickets API is one of 18 APIs that MINE publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Tickets. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 17 operations across 16 paths, and defines 57 schemas. It is described by OpenAPI 3.0.1, at version v1.0.

Requests are made against 2 base URLs: https://api.portal.saymine.com/, https://api.us.portal.saymine.com/.

17 operations 16 paths 57 schemas 5 GET12 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v1.0
Base URL
https://api.portal.saymine.com/
Authentication
API Key
Resource Areas
1

Authentication & Security 1

MINE Tickets API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer). By default, every request must be authenticated.

  • Bearer — Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your API Key in the text input below. Example: 'Bearer 12345abcdef'

Paths & Operations 17

Across 16 paths, the API surfaces 17 operations — 5 GET, 12 POST. Each is listed below with its method, path, parameters, and response codes.

Tickets 17
GET
/api/ticket/List
List all requests
10 params → 200400404
GET
/api/ticket/{ticketId}
Get ticket
1 param → 200400404401
GET
/api/ticket/{ticketId}/log
Get ticket logs
1 param → 200400404401
POST
/api/ticket/{ticketId}/dueDate
Update the due date of a request
1 param body → 200400404401
POST
/api/ticket/Create/v2
Create request [v2]
1 param body → 200202400401
POST
/api/ticket/CreateMany
Create many requests
1 param body → 200400401
GET
/api/ticket/GetMetadata
Get metadata
1 param → 200400401
POST
/api/ticket/UpdateMetadata
Update metadata
body → 200400401
POST
/api/ticket/{ticketId}/require-attention
Mark/unmark a ticket with the Require Attention label
1 param body → 200400401
POST
/api/ticket/{ticketId}/group-assignment
Assign a group to a request
1 param body → 200400401
POST
/api/ticket/AddNote
Add a note
2 params body → 200400401
POST
/api/ticket/Redact/{ticketId}
Redact request
2 params → 200
POST
/api/ticket/CloseV2
Close request
body → 200
POST
/api/ticket/EngageAutopilot/{ticketId}
Start Autopilot
1 param → 200
POST
/api/ticket/{ticketId}/custom-integrations/{integrationId}
Update custom integration status [v2]
2 params body → 200400401
GET
/api/ticket/{ticketId}/workflow
Get the workflow assigned to a ticket
1 param → 200404401
POST
/api/ticket/{ticketId}/workflow
Change the workflow assigned to a ticket
1 param body → 200400404409401

Schemas 57

The contract defines 57 schemas that model the data the API accepts and returns. The most detailed are TicketInfo (27 properties), RequestCreateWithPrivacyRightRequest (13 properties), FormCustomData (10 properties), MessageItem (10 properties). Each schema is shown below with its type and property counts.

PublicNoteResponse
object
3 properties
TicketWorkflowResponse
object
3 properties
RequestCreateResponse
object
1 property
FormCustomData
object
10 properties
SingleRequestCreateResponse
object
5 properties
ActionStatus
string
TicketCustomIntegrationStatus
string
RequestType
string
CloseTicketRequest
object
5 properties
StateChangeSource
string
StateHistoryLog
object
1 property
TicketStateEnum
string
PortalNotesResponse
object
1 property
WorkflowChangeHistoryLog
object
1 property
WorkflowChangeLogItemResponse
object
9 properties
TicketGetMetadataResponse
object
1 property
GroupAssignmentRequest
object
1 property 1 required
AuthorizedAgentInfo
object
2 properties
AssignmentLog
object
1 property
AssignedTicket
object
3 properties
TicketUpdateMetadataRequest
object
3 properties 2 required
TicketWorkflowIntegration
object
3 properties
TicketSource
string
TicketLogs
object
7 properties
NoteResponse
object
4 properties
IntegrationState
string
AssignmentLogItem
object
4 properties
TicketListItem
object
4 properties
ExternalTicketState
string
CursorTokens
object
2 properties
AutoPilotState
string
FileAttachment
object
4 properties
TicketCustomIntegrationAction
string
RequireAttentionHistoryLog
object
1 property
StateLogItem
object
7 properties
Reference
object
3 properties
RequestCreateWithPrivacyRightRequest
object
13 properties 3 required
DataSubjectTypeInfo
object
2 properties
CustomQuestion
object
3 properties
MailDirection
string
DataSubjectType
object
CustomIntegrationActionStatusRequest
object
6 properties 2 required
TicketAssignAutoPilotResponse
object
1 property
TicketInfo
object
27 properties
NoteTextRequest
object
1 property
IntegrationLogItem
object
10 properties
DueDateUpdateRequest
object
1 property
ReasonEnum
string
ChangeWorkflowRequest
object
1 property 1 required
RequireAttentionLogItem
object
6 properties
TicketMarkAsRequireAttentionRequest
object
1 property
PortalMessageResponse
object
1 property
ProcessingTaskInfo
object
5 properties
TicketCloseType
string
RequestsListResponse
object
3 properties
IntegrationHistoryLog
object
1 property
MessageItem
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mine-tickets-api-openapi.yml Raw ↑

Other APIs MINE publishes across the network.

MINE Aispm API
MINE AispmDeviceFlags API
MINE AispmEnroll API
MINE AispmEnrollmentTokens API
MINE AispmIngest API
MINE AispmInsights API
MINE AispmPublicAgents API
MINE AispmPublicDevices API
MINE Assessment API
MINE AssessmentTemplate API
MINE Employee API
MINE EvidenceSearch API
Where this information came from

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