Skip to content

List support departments

GET /api/v2/support/departments

Lists the support departments you can open a ticket in. Use departments[].slug as departmentSlug when you create a ticket with POST /api/v2/support/tickets or filter GET /api/v2/support/tickets.

Authentication: An API key with the scope read:account. About keys and scopes

Example

GET /api/v2/support/departments
curl "https://cloud.hostup.se/api/v2/support/departments" \
-H "Authorization: Bearer $HOSTUP_API_KEY"

Responses

200 The support departments.

Response 200
{
"departments": [
{
"slug": "general-web-hosting",
"displayName": "General - Web hosting",
"description": "If you need help with your current web hosting service, or anything else not listed below, we're here to help with any issues! <br> Open cases in this department if there is something general you need help with that is not related to invoicing, sales or VPS problems.<br>Available 24/7 on web hosting",
"email": "info@hostup.se"
},
{
"slug": "domain-names",
"displayName": "Domain names",
"description": "For everything related to your domain names",
"email": "registry@hostup.se"
},
{
"slug": "vps",
"displayName": "VPS",
"description": "For VPS related issues",
"email": "network-technical@hostup.se"
},
{
"slug": "billing",
"displayName": "Billing",
"description": "Frågor och funderingar angående ett köp, avbeställningar och betalningar. Vi är här för att hjälpa dig under kontorstid.",
"email": "fakturering@hostup.se"
},
{
"slug": "sales",
"displayName": "Sales",
"description": "If you are not a customer with us yet, but have questions about our services<br>If it relates to your existing services, please sign in first to gain access to open a ticket in another department.",
"email": "sales@hostup.se"
}
]
}
Response fields
departmentsarray of object
slugstring
Department slug. Use it as departmentSlug.
displayNamestring
Department name.
descriptionstring or null
What the department handles. Can contain <br> line breaks.
emailstring or null
The department’s e-mail address.

Errors

Errors are Problem Details with a stable code. Branch on the code, not on the text.

400Invalid request. The response body is an RFC 7807 Problem Details document.
401Unauthorized. Authentication is required.
403Forbidden. The caller lacks a required scope or does not own the resource.
404Not found. The resource does not exist or is not owned by the caller.
429Rate limited. Retry after the limit resets. 429 responses include Retry-After seconds plus X-RateLimit-* headers.
500Internal error. Retry later or contact support if the issue persists.