Replay a parked integration event
Reprocess a gateway event that was parked, once the cause that prevented it from producing its effect is gone.
-
Before you call it
-
The event must be published with
is_replayableset totrue— anything else returns 422. -
Fix the cause first: turn automatic invoicing back on, re-link the connected account, wait for the exchange rate.
-
It needs the write scope
integration_events:write, never the read scope of the inbox. -
What it can do
This action can have real fiscal consequences. If the cause is already resolved, the replay CAN ISSUE A REAL INVOICE, with its series number and its registration in VeriFactu. Confirm with the account owner before calling it.
-
What comes back
-
202means accepted and queued, not completed. -
The body returns the event as it stands now, not the outcome of the retry.
-
The outcome appears as a NEW event in the inbox — poll
GET /v1/integrations/eventsto see how it ended. -
It never duplicates invoices: the replay goes through the same idempotency check as the original attempt.
In: header
Path Parameters
Headers
Client-generated opaque key (up to 255 characters; UUID v7 recommended) that makes retries safe: the first response is cached and replayed for repeats without re-executing the mutation. Reusing a key with a different body returns 409 idempotency_key_reused. See the Idempotency guide. Required on this operation: repeating it delivers an effect that cannot be taken back (an email sent, a file generated, a third-party call, a charge), so a request without this header is rejected with 422 idempotency_key_required before any business logic runs.
1 <= length <= 255Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.
dateOperate on behalf of a child company (gestoría master key): pass its public id (UUID v7) and the request runs against that child's data without changing the key's scope, tier or environment (omit to use the key's own company). Invalid UUID → 400 parameter_invalid_uuid; unknown or non-owned id → 404 profile_not_found. See the Acting on behalf guide.
uuidResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json