Outbound notifications
Sovos sends a notification for each status change on your submitted documents, available through polling to your configured endpoint.
Pull notifications
Poll the GET notifications endpoint periodically as described in Monitor transmission. The response returns one or more notification objects.
Notification payload fields:
| Field | Description |
|---|---|
| id | Notification unique identifier, use for deduplication |
| taxId | The organisasjonsnummer of the submitting company |
| sourceSystemId | The ERP system ID associated with the submission |
| senderDocumentId | Your document reference from the SBDH SenderDocumentId scope |
| processType | outbound for outbound (sent) or inbound for inbound (received). |
| sciCloudStatusCode | Status code. See the status progression table in Monitor transmission. |
| errorDescription | Error detail when sciCloudStatusCode is 401 . Null otherwise |
| createdAt | Timestamp of this notification |
Note:
Notifications may not arrive in strict sequence. Before acting on a status, compare the sciCloudStatusCode against what you already have on record. Don`t assume the most recently polled notification is always the latest state. If two notifications carry the same sciCloudStatusCode, use the notification id to deduplicate.
Outbound notifications status code
| Status code | Status reason | Description |
|---|---|---|
| 102 | Validated by the sender's platform | Document was validated correctly in Compliance Network |
| 204 | Distributed | Document was sent to the buyer |
| 401 | Rejected | Document was rejected |
