Accelerate a transaction based on the payment ID. It should be used when a transaction associated with the payment is broadcasted but not confirmed for a long period of time (i.e 10 minutes). This is usually due to gas fees being too low and not picked up by any miner/validator.
The /accelerate endpoint essentially creates another transaction with the same params as the broadcasted transaction. If multiple broadcasted transactions exist, it will use the newest created one. Afterwards, OFI can sign with a higher gas fee and submit via /submit endpoint to accelerate blockchain confirmation.
Requirements for using this endpoint:
No COMPLETED transaction exist for the payment (otherwise onchain transaction has completed)
No CREATED transaction exist for the payment, otherwise OFI should sign that transaction and submit
No PENDING transaction exist for the payment, otherwise OFI should wait for transaction to be broadcasted
In another word, all existing transaction for the payment should either be FAILED (which is no longer effective) or BROADCASTED (which means they are stuck onchain and not confirmed)
Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are requred to make a successful request.
The payment id created previously. System-generated unique identifier of the resource.
"c4d1da72-111e-4d52-bdbf-2e74a2d803d5"
Accelerate a broadcasted transaction, which is stuck in mempool due to low gas fee, by broadcasting the same transaction with high gas fee.
Universally unique identifier (UUID v4) idempotency key. This key is utilized to ensure exactly-once execution of mutating requests. To create a UUIDv4 go to uuidgenerator.net. If the same key is reused, it will be treated as the same request and the original response will be returned.
"a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
Transaction accelerated successfully.
Response schema for a blockchain transaction containing details about the transaction amount, addresses, fees, and status