Retrieve notification history for a party
GET/v1/notifications
Required States: ACTIVE, VERIFIED, PROSPECT
This endpoint retrieves the notification history for a specific party with comprehensive filtering and pagination capabilities.
Authentication & Authorization:
- Requires valid party session (partyId from JWT)
- Users can only access notifications for their own party context
- Admin users can access notifications for any party using partyId parameter
Filtering Capabilities:
- partyId: Filter by specific party (Admin only - if not provided, uses JWT partyId)
- channelIdentifier: Filter by specific phone number, email, or device ID (masked in response for privacy)
- messageType: Filter by MARKETING, VERIFICATION, or GENERAL notifications
- contactChannel: Filter by SMS, EMAIL, or DEVICE notifications
- status: Filter by NEW, DELIVERED, SCHEDULED_DELIVERY, ERROR, or CANCELLED status
- fromDate/toDate: Filter by date range using ISO 8601 format (e.g., 2024-07-01T00:00:00Z)
Response Data:
- Channel identifiers are masked for privacy (e.g., +614915**06, user**@domain.com)
- Message content may be truncated or masked depending on message type and user permissions
- Includes delivery timestamps, status information, and error details if applicable
- Results are ordered by creation date (newest first)
Pagination:
- Default page size: 20 items (maximum: 100)
- Page numbers start from 1
- Response includes pagination metadata (totalPages, totalCount, hasNext, hasPrevious)
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 422
- 500
- 503
Notification history retrieved successfully
Invalid query parameters (GEN000000)
Missing or invalid authentication token (GEN001002) or Role unauthorized (GEN001006) or Tenant context could not be resolved (AUT001001)
External application access denied (AUT003001) or Party not in required status (PAR003001)
Party not found (PAR004001) or Notification not found (NOT004001)
Capability not configured for this tenant (CRT022003)
General internal server error (GEN100000) or Service error (GEN100001)
All connector targets are currently unhealthy (CRT103001)