Version 2.4.8 · latest

Package groups package-groups

Groups that organize packages so customers can browse and choose.

Pick an endpoint to see its example call on the right.

PackagesAuthentication: Admin only6 endpoints

Authentication

Send the X-API-Key header (create a key on the API Keys page; the key is shown only once at creation). An Authorization: Bearer token obtained by logging in also works.

X-API-Key

Authentication failures return 401; forbidden returns 403 (code such as insufficient_scope).

Conventions

Paging uses page (from 1) and page_size; sort with sort=field or sort=-field.

Times are RFC 3339 (UTC); amounts are in cents.

Writes return 200/201/204 on success; duplicates of a unique key return 409.

GET/api/v2/package-groupsList package groups

Authentication: Admin only

Query parameters

FieldTypeDescription
pageinteger Page number, starting from 1
Default 1
page_sizeinteger Items per page
Default 20
sortstring Sort fields, comma-separated; prefix `-` for descending, e.g. `-created_at,id`
POST/api/v2/package-groupsCreate package group

Authentication: Admin only

Request body application/json

FieldTypeDescription
desstring Description
nameRequiredstring Name
sortinteger Display order (smaller first).
POST/api/v2/package-groups/orderReorder package groups

Authentication: Admin only

Request body application/json

FieldTypeDescription
idsRequiredinteger[] Group IDs in the new order.
PUT/api/v2/package-groups/{id}Update package group

Authentication: Admin only

Request body application/json

FieldTypeDescription
desstring Description
nameRequiredstring Name
sortinteger Display order (smaller first).

Package groups object

FieldTypeDescription
created_atstring Created at
read-only
desstring Description
idinteger Record ID
read-only
idsRequiredinteger[] Group IDs in the new order.
namestring Name
sortinteger Display order (smaller first).
updated_atstring Updated at
read-only

Responses and errors

Success returns the resource JSON directly (HTTP 2xx); failures return application/problem+json (code, detail, plus errors on validation failures); lists carry items + total.

Success
{
  "id": 1,
  "name": "example"
}
List
{
  "items": [
    {
      "id": 1
    }
  ],
  "page": 1,
  "page_size": 20,
  "total": 1
}
Error
{
  "code": "validation_failed",
  "detail": "Invalid request parameters",
  "errors": [
    {
      "code": "required",
      "field": "/name",
      "message": "name is required"
    }
  ],
  "request_id": "0123456789abcdef",
  "status": 422,
  "title": "Unprocessable Entity",
  "type": "about:blank"
}
Get started

Try the live demo

Open the live demo, or contact us for a quote and the install command