> ## 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. # Redeliver a webhook delivery > Immediately replays a specific webhook delivery using the original payload. Use this after fixing your endpoint to replay a failed or retrying delivery. The delivery row is updated with the new attempt result. For production events, a failed manual redelivery re-enters the automatic retry schedule when attempts remain. `webhook.test` is always manual-only: a failed redelivery remains `failed` with `nextRetryAt: null`. **How to get `deliveryId`:** 1. Call `GET /platform/v1/organization/webhook-deliveries?status=failed` 2. Copy the `id` field from the delivery you want to replay 3. Use that value as `{deliveryId}` in this route **Example:** ```http POST /platform/v1/organization/webhook-deliveries/1f7f2e8a-2c4a-4a60-9c5b-8a1111111111/redeliver X-API-Key: hp_live_... ``` No request body is required. Hyperprop signs the replayed webhook using the same webhook signing secret and sends it to the webhook's configured URL. **Authentication:** send your organization API key in the `X-API-Key` header. ## OpenAPI ````yaml /api-reference/openapi.json post /v1/organization/webhook-deliveries/{deliveryId}/redeliver 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/{deliveryId}/redeliver: post: tags: - Webhooks summary: Redeliver a webhook delivery description: >- Immediately replays a specific webhook delivery using the original payload. Use this after fixing your endpoint to replay a failed or retrying delivery. The delivery row is updated with the new attempt result. For production events, a failed manual redelivery re-enters the automatic retry schedule when attempts remain. `webhook.test` is always manual-only: a failed redelivery remains `failed` with `nextRetryAt: null`. **How to get `deliveryId`:** 1. Call `GET /platform/v1/organization/webhook-deliveries?status=failed` 2. Copy the `id` field from the delivery you want to replay 3. Use that value as `{deliveryId}` in this route **Example:** ```http POST /platform/v1/organization/webhook-deliveries/1f7f2e8a-2c4a-4a60-9c5b-8a1111111111/redeliver X-API-Key: hp_live_... ``` No request body is required. Hyperprop signs the replayed webhook using the same webhook signing secret and sends it to the webhook's configured URL. **Authentication:** send your organization API key in the `X-API-Key` header. operationId: postV1OrganizationWebhookdeliveriesDeliveryidRedeliver parameters: - description: Webhook delivery ID x-format: guid: true name: deliveryId in: path required: true schema: type: string responses: '200': description: Redelivery result content: '*/*': schema: $ref: '#/components/schemas/Model757' '400': description: Validation failed content: '*/*': schema: $ref: '#/components/schemas/Model19' '401': description: Authentication required content: '*/*': schema: $ref: '#/components/schemas/Model9' '403': description: Access denied content: '*/*': schema: $ref: '#/components/schemas/Model47' '404': description: Resource not found content: '*/*': schema: $ref: '#/components/schemas/Model24' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model757: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model756' message: type: string example: Delivery redelivered successfully Model19: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 400 error: type: string example: Bad Request message: type: string example: Validation failed code: type: string description: Machine-readable error code — switch on this, not on message text example: VALIDATION_ERROR 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 Model24: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 404 error: type: string example: Not Found message: type: string example: Resource not found code: type: string description: Machine-readable error code — switch on this, not on message text example: NOT_FOUND 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 Model756: type: object properties: delivered: type: boolean example: true httpStatus: type: number example: 200 responseTime: type: number example: 180 delivery: $ref: '#/components/schemas/Model158' error: type: string 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) - [Inspect a webhook event and all delivery attempts](/platform-api/webhooks/inspect-a-webhook-event-and-all-delivery-attempts.md) - [View webhook delivery history](/platform-api/webhooks/view-webhook-delivery-history.md) - [Get daily webhook delivery activity](/platform-api/webhooks/get-daily-webhook-delivery-activity.md) - [Get webhook endpoint delivery and latency metrics](/platform-api/webhooks/get-webhook-endpoint-delivery-and-latency-metrics.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.