Sign Customiser

Navigation

Dark mode

Retrieve the colours section of the customiser: the heading (title) and the text under it (description) that the customer customiser shows above the colours. The colours themselves are a separate resource.

GET/api/v3/customisers/{customiser_id}/colours-section
GETGet the colours section
GET/api/v3/customisers/{customiser_id}/colours-section

Get the colours section

Retrieve the colours section of the customiser: the heading (title) and the text under it (description) that the customer customiser shows above the colours. The colours themselves are a separate resource. A customiser that has never saved this section reads the defaults (title and description null) with updated_at null, and the read does not create the section. The operation is read-only, has no side effects, and is always safe to retry. Requires the `customisers:read` scope. A 404 problem with code `resource_not_found` means the customiser does not exist on the store your API key belongs to. A 401 problem means the key is missing, invalid, or expired; a 403 problem with code `insufficient_scope` means the key lacks `customisers:read`; a 429 problem means too many requests: wait `retry_after` seconds, then retry. Error responses use RFC 9457 problem+json with a machine-readable `code` and a `request_id` to quote when contacting support.

Authorisation

The Authorization header expects a Bearer token. Generate one on the API keys page in your dashboard.

Path

The customiser id, from the list customisers operation.

Get the colours section

Click Send to see the live response.

Overview

A customiser that has never saved this section reads the defaults (title and description null) with updated_at null, and the read does not create the section. The operation is read-only, has no side effects, and is always safe to retry. Requires the customisers:read scope. A 404 problem with code resource_not_found means the customiser does not exist on the store your API key belongs to. A 401 problem means the key is missing, invalid, or expired; a 403 problem with code insufficient_scope means the key lacks customisers:read; a 429 problem means too many requests: wait retry_after seconds, then retry. Error responses use RFC 9457 problem+json with a machine-readable code and a request_id to quote when contacting support.

Authorisation

Bearer token required. Include it in the Authorization header.

Required scope: customisers:read

Path parameters

customiser_idstringpathrequired

The customiser id, from the list customisers operation.

Example: 1

Get the colours section
curl https://web.signcustomiser.com/api/v3/customisers/1/colours-section \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer YOUR_API_TOKEN'
Response
{
  "data": {
    "object": "colour_section",
    "customiser_id": 42,
    "title": "Choose your colour",
    "description": "Pick one of our colours.",
    "updated_at": "2026-05-04T09:12:31Z"
  },
  "links": {
    "self": "https://web.signcustomiser.com/api/v3/customisers/42/colours-section",
    "documentation": "https://www.signcustomiser.com/help/api/"
  },
  "meta": {
    "api_version": "v3",
    "request_id": "req_01jz9x2k7c8f3m5n6p7q8r9s0t"
  }
}

Type a question and press Enter. Use the arrow keys to move between the results.