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.
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.
/api/v2/package-groupsList package groups
Authentication: Admin only
Query parameters
| Field | Type | Description |
|---|---|---|
page | integer | Page number, starting from 1 |
page_size | integer | Items per page |
sort | string | Sort fields, comma-separated; prefix `-` for descending, e.g. `-created_at,id` |
/api/v2/package-groupsCreate package group
Authentication: Admin only
Request body application/json
| Field | Type | Description |
|---|---|---|
des | string | Description |
nameRequired | string | Name |
sort | integer | Display order (smaller first). |
/api/v2/package-groups/orderReorder package groups
Authentication: Admin only
Request body application/json
| Field | Type | Description |
|---|---|---|
idsRequired | integer[] | Group IDs in the new order. |
/api/v2/package-groups/{id}Get package group
Authentication: Admin only
/api/v2/package-groups/{id}Update package group
Authentication: Admin only
Request body application/json
| Field | Type | Description |
|---|---|---|
des | string | Description |
nameRequired | string | Name |
sort | integer | Display order (smaller first). |
/api/v2/package-groups/{id}Delete package group
Authentication: Admin only
Package groups object
| Field | Type | Description |
|---|---|---|
created_at | string | Created at |
des | string | Description |
id | integer | Record ID |
idsRequired | integer[] | Group IDs in the new order. |
name | string | Name |
sort | integer | Display order (smaller first). |
updated_at | string | Updated at |
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.
{
"id": 1,
"name": "example"
}{
"items": [
{
"id": 1
}
],
"page": 1,
"page_size": 20,
"total": 1
}{
"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"
}