Overview
This endpoint enables registered services to submit decision requests for human review. The notification can include various types of actions that request different forms of user input.Request
Endpoint:POST /api/v1/notifications
Authentication: Requires Bearer token using service API key
Request Body
The request body should contain a complete notification object as defined in the Message Formats section. Here’s a simplified example:Response
Success Response
Status Code:201 Created
Field | Type | Description |
---|---|---|
notification_id | string | Unique identifier for tracking the notification |
status | string | Current notification state, initially “created” |
estimated_delivery | datetime | Projected delivery timestamp in ISO 8601 format |
notification_id
for correlation with subsequent webhook callbacks.
Error Responses
Status Code | Error Code | Description |
---|---|---|
400 Bad Request | MISSING_REQUIRED_FIELD | Required field is missing from request |
400 Bad Request | INVALID_RESPONSE_TYPE | Unknown response type specified |
400 Bad Request | MALFORMED_ACTION | Action definition is incomplete or invalid |
401 Unauthorized | AUTH_INVALID_TOKEN | Service API key is invalid |
403 Forbidden | SERVICE_SUSPENDED | Service has been temporarily suspended |
422 Unprocessable Entity | CONSTRAINT_VIOLATION | Request violates defined constraints |
429 Too Many Requests | RATE_LIMIT_EXCEEDED | Rate limit for notification creation exceeded |
Examples
cURL Example
Python Example
Best Practices
- Always include a descriptive title and detailed description
- Set appropriate deadlines based on the urgency of the decision
- Choose the most appropriate response type for each action
- Include relevant flags to communicate action characteristics
- Add contextual metadata to help users make informed decisions
- Keep attachments small and relevant