Skip to main content

Open a support ticket

Support tickets are the way to reach the Paradarum team for anything that isn't answered by self-service docs. You open them from your dashboard, attach an optional file, and follow the conversation by email and Telegram.

Where to open a ticket​

In the Paradarum panel, go to Help & Support → Contact (the "Support Tickets" page). From there:

  1. The list view shows every ticket on your account, with its subject, status badge, topic badge, optional property, created date, and message count. If you have none yet, an empty state invites you to create one.
  2. Click New Ticket to switch to the create form.
  3. Fill in the fields described below.
  4. Click Submit Ticket.

:::info Authentication required There is no public or anonymous ticket API. You must be signed in to the panel, and every ticket belongs to your account. New tickets always start in the Open status. :::

Ticket fields​

FieldRequiredNotes
SubjectYesSingle-line text, max 200 characters (enforced client- and server-side).
DescriptionYesMulti-line text. No length cap.
PropertyNoDropdown of your account's properties. Defaults to General question (no property).
TopicYesOne of six categories. Defaults to General. See Categories & statuses.
Attach FileNoOne file, up to 10 MB. See Replies & closing.

:::tip Link a property when it's specific If your issue affects one site, pick it from the Property dropdown so the team has context immediately. Leave it as General question for billing, account, or cross-property questions. :::

Create a ticket via the API​

Tickets are created with POST /api/Ticket. The accountId is a required query-string parameter on every ticket endpoint — it is not part of the JSON body or the path. All calls are authenticated with a Bearer token.

curl -X POST "https://api.paradarum.com/api/Ticket?accountId=123" \
  -H "X-API-Key: pdm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "subject": "SSL certificate not provisioning",
    "description": "My site example.com shows a TLS error after adding the domain.",
    "topic": 4,
    "propertyId": 55
  }'

Here topic: 4 is SSL. Omit propertyId (or send null) for a general question.

Request body​

The body is a CreateTicketRequest:

{
  "subject": "string (required, max 200 chars)",
  "description": "string (required)",
  "propertyId": 55,
  "topic": 4
}
  • propertyId is optional. If supplied, it must belong to your account, or the server returns 400 Invalid property.
  • topic is the integer value of the topic enum and defaults to 0 (General).

Success response​

On success the API returns 201 with the standard envelope:

{
  "succeeded": true,
  "message": "Ticket created successfully.",
  "data": {
    "id": 789,
    "subject": "SSL certificate not provisioning",
    "status": 0,
    "topic": 4,
    "propertyId": 55,
    "propertyName": "example.com"
  },
  "pageNumber": 0,
  "pageSize": 0,
  "totalPages": 0,
  "totalRecords": 0
}

:::warning Empty subject or description The server returns 400 if either subject or description is empty. Subject is also capped at 200 characters. :::

Create flow at a glance​

Notifications​

When a ticket is created — and on later updates — Paradarum sends fire-and-forget notifications by email and Telegram to the ticket's user, and notifies admins when you reply.

:::note Delivery isn't guaranteed Notifications are best-effort: a delivery failure never fails the API call, but it also means a message could be missed. Check the Contact page in your dashboard for the authoritative state of a ticket. :::

Next steps​