Support SPI
Implement the SPI so Premex Support can list, fetch, post, and close conversations in your backend.
Support SPI (full spec)
The Support SPI is the integration API that lets Premex Support use your backend as the system of record for conversations. Full spec is required: you must implement every endpoint and schema defined in the OpenAPI spec.
Endpoints
| Method | Path | Description |
|---|---|---|
| GET | /care/conversations?customerId | List conversations for a specific customer. |
| POST | /care/conversations | Create a new conversation. |
| GET | /care/conversations/{conversationId}?customerId | Fetch conversation detail including messages. |
| POST | /care/conversations/{conversationId}/messages | Post a message into an existing conversation. |
| POST | /care/conversations/{conversationId}/close | Resolve or close a conversation. |
Compliance rules (required)
- Every endpoint above must exist and match the request/response shapes.
- All date-time fields must be ISO 8601 timestamps.
- IDs must be stable and unique. We recommend opaque IDs (UUIDv4) for
conversationIdandmessageId. - Customer scoping is mandatory: every request is scoped by
customerId. Product scoping is handled by the base URL configuration. - Status must be one of:
new | waiting-for-agent | waiting-for-customer | resolved | closed | unknown
Next: endpoint details
See the detailed reference for payloads and examples: /docs/spi/endpoints.