Partner API
All routes live under /partner/v1/organisations/{partnerId}/listings and need a partner token
(Authorization: Bearer ciqra_pt_...) from ciqra auth login. The organisation in the path is checked against
your user on every call.
| Method and path | What it does |
|---|---|
GET /listings |
Your organisation’s submissions, newest first. |
GET /listings/{id} |
One submission with its status, note, reviewer and manifest. |
PUT /listings |
Create the draft of (key, version), or replace the manifest of an editable one. Body: { "manifest": { ... } }. |
POST /listings/{id}/submit |
Hand a draft to review. |
POST /listings/{id}/reopen |
Turn a rejected submission back into a draft. |
Writing needs the Owner, Admin or Developer role; reading is open to every member.
Errors
Section titled “Errors”An error is { "error": "<code>", "message": "...", "findings": [...] }.
| Status | error |
When |
|---|---|---|
| 422 | invalid_manifest |
The manifest has errors. findings lists every one as { field, message, isError }. |
| 409 | key_taken |
Another organisation already uses this key. |
| 409 | version_locked |
That version is already submitted: publish a new version. |
| 409 | invalid_transition |
The status does not allow that move. |
| 409 | conflict |
Two saves of a new version raced: try again. |
| 404 | not_found |
No such submission in your organisation. |
| 403 | forbidden |
You are not a member, or your role may not do that. |
| 400 | validation_failed |
A malformed request. |
For the reviewer’s side (the decisions take, approve, reject, list, suspend, delist), note_required
is returned when a rejection, suspension or delisting has no reason, and reviewer_required when no named reviewer
is attached. Those routes are CIQRA’s, not yours; they are listed so a status change is never a surprise.