> ## Documentation Index > Fetch the complete documentation index at: https://docs.hyperprop.com/llms.txt > Use this file to discover all available pages before exploring further. # View webhook delivery history > Paginated log of all webhook delivery attempts across your organization. **Use cases:** - Debug failed deliveries — see HTTP status codes and response bodies - Audit which events were sent and when - Monitor retry progress for failing endpoints - Copy a delivery `id` and replay it with the redelivery endpoint **Filter options:** - `webhookId` — Show deliveries for a specific webhook only - `eventType` — Filter by event type (e.g. `account.status_changed`) - `status` — Filter by delivery status: `pending`, `delivered`, `retrying`, `failed` **Delivery statuses:** | Status | Meaning | |--------|---------| | `pending` | Queued, not yet attempted | | `delivered` | Successfully delivered (2xx response) | | `retrying` | Failed, will retry (up to 5 attempts over ~2.5 hours) | | `failed` | All retries exhausted | **Replay a failed delivery:** 1. List failed deliveries: ```http GET /platform/v1/organization/webhook-deliveries?status=failed ``` 2. Copy the delivery `id` from the response. The delivery `id` is the value used as `{deliveryId}`. It is different from `eventId` and `webhookId`. ```json { "success": true, "data": { "deliveries": [ { "id": "1f7f2e8a-2c4a-4a60-9c5b-8a1111111111", "webhookId": "8a6b1d4c-9f3e-4f2b-a111-222222222222", "eventId": "4c2c49f0-7f1a-4f40-b333-333333333333", "eventType": "account.failed", "status": "failed", "httpStatus": 500, "attempt": 5 } ] } } ``` 3. Replay that exact delivery: ```http POST /platform/v1/organization/webhook-deliveries/{deliveryId}/redeliver ``` The replay uses the original payload and returns the new delivery result. **Authentication:** send your organization API key in the `X-API-Key` header. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/organization/webhook-deliveries openapi: 3.0.0 info: title: Hyperprop Platform API version: 1.0.0 description: >- REST API for the Hyperprop Trading Platform — provision evaluation and funded trading accounts, manage traders and plans, react to account lifecycle events via signed webhooks, and reconcile billing. Built for prop firms integrating from their own backend. Authentication, quick start, error handling, idempotency, pagination, custom metadata, webhooks, and the MCP connector are documented at https://docs.hyperprop.com. x-logo: url: https://app.hyperprop.com/logo-icon.svg altText: Hyperprop href: https://hyperprop.com servers: - url: https://api.hyperprop.com/platform description: Production security: [] tags: - name: Trading accounts description: Create, update, and inspect trading accounts. - name: Traders description: Look up and update the traders in your organization. - name: Trading plans description: Define the plans you sell. - name: Trading rules description: Define how accounts are evaluated. - name: Lockouts description: Pause and resume trading on an account. - name: Payouts description: Check payout eligibility and record payouts. - name: Purchases description: Purchases recorded for your organization. - name: Time Machine description: Restore accounts to an earlier trading day or instant. - name: Webhooks description: Register webhook endpoints and inspect deliveries. - name: Events description: Your organization's event history and real-time event stream. - name: Reconciliation description: Balances, end-of-day snapshots, and fills for reconciliation. - name: Analytics description: Organization performance and plan economics. - name: Billing description: 'Your Hyperprop bill: activity, billing cycles, and forecasts.' - name: Team and roles description: Manage dashboard access for your staff. - name: API keys description: Manage your organization's API key. - name: Logs and health description: API request logs, the audit log, and integration health. - name: Organization profile description: Your organization's profile and logo. - name: Support description: Open and follow up on support tickets. - name: Partner access description: >- Read a trader's journal as an approved partner app, with the trader's own key. paths: /v1/organization/webhook-deliveries: get: tags: - Webhooks summary: View webhook delivery history description: >- Paginated log of all webhook delivery attempts across your organization. **Use cases:** - Debug failed deliveries — see HTTP status codes and response bodies - Audit which events were sent and when - Monitor retry progress for failing endpoints - Copy a delivery `id` and replay it with the redelivery endpoint **Filter options:** - `webhookId` — Show deliveries for a specific webhook only - `eventType` — Filter by event type (e.g. `account.status_changed`) - `status` — Filter by delivery status: `pending`, `delivered`, `retrying`, `failed` **Delivery statuses:** | Status | Meaning | |--------|---------| | `pending` | Queued, not yet attempted | | `delivered` | Successfully delivered (2xx response) | | `retrying` | Failed, will retry (up to 5 attempts over ~2.5 hours) | | `failed` | All retries exhausted | **Replay a failed delivery:** 1. List failed deliveries: ```http GET /platform/v1/organization/webhook-deliveries?status=failed ``` 2. Copy the delivery `id` from the response. The delivery `id` is the value used as `{deliveryId}`. It is different from `eventId` and `webhookId`. ```json { "success": true, "data": { "deliveries": [ { "id": "1f7f2e8a-2c4a-4a60-9c5b-8a1111111111", "webhookId": "8a6b1d4c-9f3e-4f2b-a111-222222222222", "eventId": "4c2c49f0-7f1a-4f40-b333-333333333333", "eventType": "account.failed", "status": "failed", "httpStatus": 500, "attempt": 5 } ] } } ``` 3. Replay that exact delivery: ```http POST /platform/v1/organization/webhook-deliveries/{deliveryId}/redeliver ``` The replay uses the original payload and returns the new delivery result. **Authentication:** send your organization API key in the `X-API-Key` header. operationId: getV1OrganizationWebhookdeliveries parameters: - description: Filter by webhook ID x-format: guid: true name: webhookId in: query required: false schema: type: string - description: Filter by event type name: eventType in: query required: false schema: type: string - description: Filter by delivery status name: status in: query required: false schema: type: string enum: - pending - delivered - retrying - failed - description: Results per page (max 100) name: limit in: query schema: type: integer minimum: 1 maximum: 100 default: 50 - description: Offset for pagination name: offset in: query schema: type: integer minimum: 0 default: 0 responses: '200': description: Delivery history content: '*/*': schema: $ref: '#/components/schemas/Model162' '401': description: Authentication required content: '*/*': schema: $ref: '#/components/schemas/Model9' '403': description: Access denied content: '*/*': schema: $ref: '#/components/schemas/Model47' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model162: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model161' Model9: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 401 error: type: string example: Unauthorized message: type: string example: Authentication required code: type: string description: Machine-readable error code — switch on this, not on message text example: UNAUTHORIZED Model47: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 403 error: type: string example: Forbidden message: type: string example: Access denied code: type: string description: Machine-readable error code — switch on this, not on message text example: FORBIDDEN Model5: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 500 error: type: string example: Internal Server Error message: type: string example: An unexpected error occurred code: type: string description: Machine-readable error code — switch on this, not on message text example: INTERNAL_ERROR Model161: type: object properties: deliveries: $ref: '#/components/schemas/Model159' pagination: $ref: '#/components/schemas/Model160' Model159: type: array items: $ref: '#/components/schemas/Model158' Model160: type: object properties: total: type: number example: 142 limit: type: number example: 50 offset: type: number example: 0 hasMore: type: boolean example: true Model158: type: object properties: id: type: string x-format: guid: true webhookId: type: string x-format: guid: true eventId: type: string x-format: guid: true eventType: type: string example: account.status_changed endpointUrl: type: string example: https://your-server.com/webhooks/hyperprop webhookDescription: type: string example: Production webhook status: $ref: '#/components/schemas/Model157' httpStatus: type: number example: 200 responseBody: type: string example: '{"received":true}' responseHeaders: $ref: '#/components/schemas/responseHeaders' responseTime: type: number example: 245 attempt: type: number example: 1 nextRetryAt: type: string deliveredAt: type: string createdAt: type: string Model157: type: string example: delivered enum: - pending - delivered - retrying - failed responseHeaders: type: object securitySchemes: X-API-Key: type: apiKey name: X-API-Key in: header description: >- Organization API key. Format: "hp_live_{key}". Organization admins manage the key in the dashboard. ```` ## Related topics - [Inspect one event and all its webhook deliveries](/platform-api/events/inspect-one-event-and-all-its-webhook-deliveries.md) - [Get webhook endpoint delivery and latency metrics](/platform-api/webhooks/get-webhook-endpoint-delivery-and-latency-metrics.md) - [Get daily webhook delivery activity](/platform-api/webhooks/get-daily-webhook-delivery-activity.md) - [Inspect a webhook event and all delivery attempts](/platform-api/webhooks/inspect-a-webhook-event-and-all-delivery-attempts.md) - [Delete a webhook](/platform-api/webhooks/delete-a-webhook.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.