Skip to main content
Use support endpoints to manage partner support tickets and respond to customer support tickets visible to your partner organization. Required permissions depend on the action:

Create a partner ticket

You can create a partner ticket directly with POST /api/v1/support/partner-tickets. If you do not need attachments, draftId is optional.
Optional fields:

Add attachments to a new partner ticket

Attachments require a draft. Create the draft first, upload attachments to that draft, then submit the ticket with the same draftId.
The multipart field name must be exactly file. Multipart requests use Nuvera’s canonical multipart body hash. See Multipart body hash before implementing uploads.

List and read partner tickets

Use GET /api/v1/support/partner-tickets to list partner tickets and GET /api/v1/support/partner-tickets/{ticketId} to read one ticket.
Query fields: For attachments already on a partner ticket, request a download URL with GET /api/v1/support/partner-tickets/{ticketId}/attachments/{attachmentId}/download-url.

Reply to a partner ticket

Replies require a reply draft. Create the reply draft, optionally upload attachments to it, then submit the reply with that draftId.
Optional reply field:

Reply to customer tickets

Partner REST can list, read, and reply to customer tickets for the partner organization. It does not expose an endpoint to create a customer ticket.
Customer ticket list supports the same query fields as partner ticket list, plus optional customerId and optional customerMatchState with values MATCHED, UNMATCHED, or AMBIGUOUS. To reply, create a reply draft with POST /api/v1/support/customer-tickets/{ticketId}/reply-drafts, optionally upload attachments with POST /api/v1/support/customer-tickets/{ticketId}/reply-drafts/{draftId}/attachments, then submit the reply with POST /api/v1/support/customer-tickets/{ticketId}/replies. For complete support endpoint details, open the API Reference.