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

Suger Support API

Access to Suger Support ticket resources

Suger Support API is one of 11 APIs that Suger publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Support. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 8 operations across 6 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.suger.cloud.

8 operations 6 paths 12 schemas 2 GET3 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.suger.cloud
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Suger Support API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (APIKeyAuth).

  • APIKeyAuth — API Key for authorization in format of .

Paths & Operations 8

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

Support 8

Access to Suger Support ticket resources

GET
/org/{orgId}/support/ticket
List Support Tickets
ListSupportTickets 3 params → 200400500
POST
/org/{orgId}/support/ticket
Create Support Ticket
CreateSupportTicket 1 param body → 200400500
GET
/org/{orgId}/support/ticket/{ticketId}
Get Support Ticket
GetSupportTicket 2 params → 200400500
PATCH
/org/{orgId}/support/ticket/{ticketId}
Update Support Ticket
UpdateSupportTicket 2 params body → 200400500
POST
/org/{orgId}/support/ticket/{ticketId}/attachment
Create Support Ticket Attachment
CreateSupportTicketAttachment 2 params body → 200400500
PATCH
/org/{orgId}/support/ticket/{ticketId}/close
Close Support Ticket
CloseSupportTicket 2 params → 200400500
POST
/org/{orgId}/support/ticket/{ticketId}/comment
Create Support Ticket Comment
CreateSupportTicketComment 2 params body → 200400500
PATCH
/org/{orgId}/support/ticket/{ticketId}/reopen
Reopen Support Ticket
ReopenSupportTicket 2 params → 200400500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are SupportTicket (13 properties), SupportTicketAttachment (9 properties), SupportTicketImage (9 properties), SupportTicketUser (5 properties). Each schema is shown below with its type and property counts.

CreateSupportTicketAttachment_request
object
1 property 1 required
SupportTicket
object
13 properties
SupportTicketAttachment
object
9 properties
SupportTicketImage
object
9 properties
UpdateSupportTicketRequest
object
2 properties 2 required
SupportTicketFrame
object
2 properties
SupportTicketComment
object
5 properties
SupportTicketStatus
string
SupportTicketPriority
string
SupportTicketCommentDetail
object
5 properties
SupportTicketUser
object
5 properties
ListSupportTicketsResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

suger-support-api-openapi.yml Raw ↑

Other APIs Suger publishes across the network.

Suger API API
Suger Billing API
Suger Buyer API
Suger Contact API
Suger Entitlement API
Suger Metering API
Suger Notification API
Suger Offer API
Suger Product API
Suger Report API
Where this information came from

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