> ## Documentation Index > Fetch the complete documentation index at: https://docs.journeybee.io/llms.txt > Use this file to discover all available pages before exploring further. # Replay a v2 event delivery > Re-sends the stored request body of an earlier delivery byte for byte — same `Journeybee-Event-Id`, a new `Journeybee-Delivery-Id`, a fresh signature timestamp signed with every live secret at send time. The record and the subscription filter are never re-read. The replay is a new delivery chain (the response's `uuid` is the new delivery; the log links it to the ROOT delivery via `replay_of_delivery_uuid` — replaying a replay resolves to the root) on the same queue and retry policy. Unknown or foreign subscriptions and deliveries, a delivery under another subscription, a delivery past the 30-day retention, and a replay whose root is gone all return the same 404. A scoped credential must also hold the read grant for the delivery's resource (e.g. `leads:read` for a lead event) or gets 403. Returns 409 `subscription_not_active` while the subscription is not active, 409 `replay_body_unavailable` when the stored body was not retained, and 429 above 60 replays per minute per subscription or 300 per minute per company. ## OpenAPI ````yaml /openapi.json post /event-subscriptions/{uuid}/deliveries/{id}/replay openapi: 3.1.0 info: title: Journeybee API description: >- Public REST API for the Journeybee PRM platform. Manage partners, leads, deals, products, pricing calculators, tasks, and more programmatically. All endpoints require authentication via API key. Use `Authorization: Bearer ` or `Api-Key ` header. See the [Authentication guide](/guides/authentication) for details. version: 1.0.0 servers: - url: https://api.journeybee.io/v1 description: Production security: - apiKey: [] tags: - name: Account description: >- Authenticated company account info, API key permissions, and enabled modules - name: Analytics description: >- Dashboard analytics and reporting — commission, engagement, LMS, and partner revenue metrics - name: Assets description: File and media asset management - name: Attributions description: Attribution type definitions - name: Audit Log description: Unified audit log of company activity (read-only) - name: Automations description: Workflow automation rule configurations - name: Campaign Audience description: Audience filters on a campaign - name: Campaign Partners description: Partners shared into a campaign audience - name: Campaigns description: Partner marketing campaigns - name: Card Assignees description: Assigned users on a card - name: Card Partners description: Partners linked to a card - name: Card Tags description: Tags on a card - name: Cards description: Kanban project cards - name: Categories description: Partner categories - name: Certification Categories description: Categories on a certification - name: Certification Enrollments description: User enrollments in a certification - name: Certification Folders description: Folders on a certification - name: Certification Resources description: Curriculum resources in a certification - name: Certifications description: LMS certifications - name: Commissions description: >- Commission rule configurations with calculation entries, tier/category/partnership scoping - name: Contacts description: Partner contacts across partnerships - name: Currencies description: Available currencies - name: Custom Field Options description: Options on select/multi-select custom fields - name: Custom Field Rules description: Visibility and requirement rules on custom fields - name: Custom Field Values description: Custom field values - name: Custom Fields description: Custom field definitions - name: Deal Commission description: Commission calculation on a deal - name: Deal Custom Field Values description: Custom field values on a deal - name: Deal Notes description: Notes on a deal - name: Deal Payments description: Payment records on a deal (read-only) - name: Deal Products description: Products attached to a deal - name: Deal Stages description: Deal pipeline stages - name: Deal Tags description: Tags on a deal - name: Deal Tasks description: Tasks on a deal - name: Deals description: Deal management - name: Event Subscriptions - name: Event Types - name: Folders description: Content folders - name: Integrations description: Company integration settings - name: Lead Attributions description: Attribution records on a lead - name: Lead Contacts description: Partner contacts on a lead - name: Lead Custom Field Values description: Custom field values on a lead - name: Lead Distributor description: Distributors for a lead - name: Lead Notes description: Notes on a lead - name: Lead Products description: Products attached to a lead - name: Lead Quotes description: >- Quotes on a lead — generated from pricing calculators with line items and totals - name: Lead Tags description: Tags on a lead - name: Lead Tasks description: Tasks on a lead - name: Lead Users description: Assigned users on a lead - name: Leads description: Lead management - name: Marketing Templates description: Marketing email templates - name: Partner Contacts description: Contacts on a partner - name: Partner Custom Field Values description: Custom field values on a partner - name: Partner Domains description: Domains on a partner - name: Partner Notes description: Notes on a partner - name: Partner Resellers description: Reseller assignments on a distributor - name: Partner Stages description: Partner pipeline stages - name: Partner Tags description: Tags on a partner - name: Partner Users description: Assigned users on a partner - name: Partners description: Core partner CRUD - name: Pricing Calculator Fields description: Input fields on a pricing calculator - name: Pricing Calculator Formulas description: Discount/tax/surcharge formulas on a pricing calculator - name: Pricing Calculator Products description: Products attached to a pricing calculator - name: Pricing Calculators description: Pricing calculator configurations - name: Products description: Product catalog - name: Resource Blocks description: Content blocks within a resource - name: Resource Categories description: Categories on a resource - name: Resource Folders description: Folders on a resource - name: Resource Tags description: Tags on a resource - name: Resources description: Learning resources - name: Room Blocks description: Content blocks within a room - name: Room Categories description: Category-based room access control - name: Room Partnerships description: Direct partnership room access - name: Room Stages description: Stage-based room access control - name: Room Tags description: Tag-based room access control - name: Room Tiers description: Tier-based room access control - name: Rooms description: Partner portal rooms - name: Tags description: Tag definitions - name: Task Users description: Assigned users on a task - name: Tasks description: Task management - name: Tiers description: Partner tiers - name: Users description: Company team members - name: Webhook Events description: Outbound webhook payloads sent to your configured URLs when events occur paths: /event-subscriptions/{uuid}/deliveries/{id}/replay: post: tags: - Event Subscriptions summary: Replay a v2 event delivery description: >- Re-sends the stored request body of an earlier delivery byte for byte — same `Journeybee-Event-Id`, a new `Journeybee-Delivery-Id`, a fresh signature timestamp signed with every live secret at send time. The record and the subscription filter are never re-read. The replay is a new delivery chain (the response's `uuid` is the new delivery; the log links it to the ROOT delivery via `replay_of_delivery_uuid` — replaying a replay resolves to the root) on the same queue and retry policy. Unknown or foreign subscriptions and deliveries, a delivery under another subscription, a delivery past the 30-day retention, and a replay whose root is gone all return the same 404. A scoped credential must also hold the read grant for the delivery's resource (e.g. `leads:read` for a lead event) or gets 403. Returns 409 `subscription_not_active` while the subscription is not active, 409 `replay_body_unavailable` when the stored body was not retained, and 429 above 60 replays per minute per subscription or 300 per minute per company. operationId: replayEventSubscriptionDelivery parameters: - schema: type: string format: uuid pattern: >- ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$ in: path name: uuid required: true - schema: type: string minLength: 1 maxLength: 64 in: path name: id required: true responses: '202': description: Default Response content: application/json: schema: type: object properties: uuid: type: string description: >- Public id of the new delivery created by this replay (`dlv_...`). status: type: string description: >- Delivery status — always `pending` on the accepted response. enum: - pending required: - uuid - status additionalProperties: false components: securitySchemes: apiKey: type: http scheme: bearer description: API key authentication. Use "Bearer " or "Api-Key ". ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.