Support, evidence attachments and incident reports

Choose a support channel#

Use Contact, Help & Support or the available support chat entry in Vega. Include context relevant to the issue: requests and clients for API integration, orders for payments, and task, Room and harness details for agents.

Image and file evidence#

Support chat accepts images and files, up to five attachments per message and 10 MiB per file. Confirm uploaded attachments appear in the message. Include complete errors and relevant timing in screenshots while redacting passwords, keys and full card numbers.

If an upload fails, check size, type and network before retrying that attachment. Include a written description alongside evidence rather than only reporting that something failed.

An actionable incident report#

A request id helps correlate client errors with service logs, but its suffix or data-center code alone cannot identify whether the gateway or provider caused the failure. Preserve the error body and retry headers for diagnosis.

Time and timezone:
Feature / endpoint:
Model and client version:
HTTP status / error code:
Request ID or task ID:
Order ID (payment issues only):
Expected result:
Actual result:
Minimal reproduction (without credentials):