Solution Overview for Business Users / Version 2506.0
Table Of Contents| Return Code | Message | Description |
|---|---|---|
400 (Bad Request) | Missing input | The required JSON body is missing. |
Invalid ID | The ID given for GET/PUT/DELETE requests on individual subscriptions is not a valid UUID. | |
Input cannot be deserialized | The given request body is no valid JSON according to the spec. This can be generally malformed input or,for example, misspelled enum values. | |
Namespace '<name>' is forbidden | The calling user doesn’t have sufficient rights to use the requested subscription namespace. | |
Namespace 'PUBLIC' does not allow endpoint type '<endpoint_type>' | Only webhook endpoints are allowed for the PUBLIC namespace. | |
Namespace 'PUBLIC' does not allow subscription of '<event_type>' events | The PUBLIC namespace only allows the subscription to CONTENT, NOTIFICATION and WORKFLOW events. | |
Use of service name is reserved | A subscription with 'PUBLIC' namespace must not define a service name. | |
Service name is required | Only relevant for internal subscriptions. An internal subscription must have a service name. | |
Namespace is immutable | The namespace assigned when creating a subscription cannot be changed when updating the subscription. | |
<property path> <message> | A property within the submitted JSON has a validation error, that is, a null value where a value is required. | |
409 (Conflict) | Duplicate endpoint '<endpoint_url>' | A specific endpoint can only be used once per event type. |
Maximum number of 10 subscriptions reached | The total number of subscriptions is limited to 10. | |
Maximum number of 4 subscriptions for stream '<stream_type>' reached | The total number of subscriptions per event type is limited to 4. |
Table 12.1. Table of error codes and Messages


