This endpoint broadcasts a signed transaction payload to the blockchain for an allowance operation. It's used when the client wants the server to submit the transaction to the blockchain on their behalf.
The request requires the signed transaction payload in the request body. This endpoint is typically called after a user has signed the transaction payload but wants the server to handle the actual broadcasting to the blockchain network.
This endpoint is primarily used with wallet as API solutions such as our Integrated wallet, where integrators using this endpoint must implement a custom signature system on their side to handle cryptographic signing of the payloads prior to submission.
Successful execution of this endpoint will submit the transaction to the blockchain and track its status, with no additional action required from the client.
Access level: Only qualified investors of the token who initiated the original allowance transaction can broadcast the transaction payload.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Transaction broadcasted successfully.
Broadcast Transaction operation failed due to invalid data.
Transaction payload is not properly signed.
Transaction signer does not match expected wallet address.
Invalid transaction format or structure.
Transaction parsing failed: data too short.
Invalid hex string format.
Transaction is not signed.
Signer mismatch. Expected wallet address does not match actual signer.
Workflow is not in a valid status to log a transaction.
Task already completed.
You cannot modify a workflow that does not belong to you.
Token not manageable with this authentication.
Token not found.
Alowance workflow not found.
Allowance workflow task not found.