Retry Transfer
POST /v1/transfers//retry
Retry a failed or retryable transfer for the authenticated organization.
Documentation Index
Fetch the complete documentation index at: https://docs.waycore.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Opaque API key passed as Authorization: Bearer <key>. Keys are organization-bound, environment-bound (live or test), scope-carrying, and expiring. Create and manage keys via the console.
Headers
Optional caller-generated key used to safely retry create and retry requests. When provided, the key is assumed to identify one request for at least 24 hours: identical retries may return a replayed response and materially different payloads with the same key should return 409 Conflict.
1 - 255^\S(?:.*\S)?$Path Parameters
Stable transfer identifier.
Response
Successful Response
Stable transfer identifier.
Current transfer lifecycle status. pending_bank_approval means Waycore has initiated the bank flow and the integrator should direct its user to approve in the bank portal.
queued, executing, pending_bank_approval, completed, failed, returned, cancelled, unknown Transfer direction.
internal, external Amount requested by the caller.
{
"currency": "USD",
"type": "money",
"value": "1250.00"
}
Source connected account identifier.
Transfer destination.
- InternalAccountDestination
- MaskedExternalAccountDestination
Transfer rail used or requested.
internal, ach, wire, swift, fednow, rtp, sepa, local Integrator-supplied payment reference distinct from the idempotency key. Where supported by the bank, this is the reference sent with the payment.
When the transfer was created.
When the transfer last changed.
Actual amount sent once execution is known.
{
"currency": "USD",
"type": "money",
"value": "1250.00"
}
Integrator-visible memo.
Failure details when status is failed, returned, or cancelled.