Create transaction-related issues (for example, settlement delays, missing information, or refunds). These tickets are stored centrally in the CPN platform and routed to the appropriate party for resolution.
Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are requred to make a successful request.
Request schema for creating a support ticket
System-generated unique identifier of the resource.
"c4d1da72-111e-4d52-bdbf-2e74a2d803d5"
Type of the support ticket
PAYMENT_SETTLEMENT_DELAY, PAYMENT_SENT_TO_WRONG_RECIPIENT, PAYMENT_AMOUNT_INCORRECT, REQUEST_FOR_INFORMATION_OFI, REQUEST_FOR_INFORMATION_SENDER, REQUEST_FOR_INFORMATION_RECEIVER, FUNDING_AMOUNT_DISCREPANCY, REVERSE_FUNDS, EXISTING_TICKET, OTHER "PAYMENT_SETTLEMENT_DELAY"
Detailed message for the support ticket.
Contact email for follow-up.
"help@ofi.com"
Universally unique identifier (UUID v4) idempotency key. This key is utilized to ensure exactly-once execution of mutating requests. To create a UUIDv4 go to uuidgenerator.net. If the same key is reused, it will be treated as the same request and the original response will be returned.
"a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
Optional CC email address for follow-up conversations on this support ticket.
[
"ccsupport01@example.com",
"ccsupport02@example.com"
]Support ticket created successfully.
Response schema for a support ticket