Skip to main content
POST
/
operations
/
set-approval
Toggle setApprovalForAll
curl --request POST \
  --url https://relayer.forka.st/operations/set-approval \
  --header 'Content-Type: application/json' \
  --data '
{
  "operator": "0x4d97dcd97ec945f40cf65f87097ace5ea0476045",
  "approved": true,
  "contract": "0xCeAfDb29f9fC7c25fF6F0768d45b288c9b7C5cA5"
}
'
{
  "txHash": "0x0123...",
  "confirmations": 1
}
Instruct the relayer to toggle setApprovalForAll on the Conditional Tokens contract (or a custom address). This enables the operator to move outcome tokens before Safe deployments are available.
Send requests to https://relayer.forka.st/operations/set-approval with the usual L2 headers. The relayer signs on behalf of its custodial address and returns the broadcast transaction hash.

​
Request body

FieldTypeRequiredDescription
operatorstringYesAddress that should gain or lose setApprovalForAll privileges.
approvedbooleanYestrue to grant approvals, false to revoke.
contractstringNoERC-1155 contract to target. Defaults to the Conditional Tokens address when omitted.

​
Notes

  • When contract is omitted, the relayer uses the default Conditional Tokens deployment for the connected chain.
  • Approval toggles are idempotent; requesting approved: true twice yields the same response while keeping confirmations accurate.
  • Errors surface as 400 (validation) or 502 (RPC broadcast). Check the returned error field for troubleshooting details.

Body

application/json
​
operator
string
required
​
approved
boolean
required
​
contract
string

Conditional Tokens contract. Defaults to production address when omitted.

Response

Transaction broadcast by the relayer.

​
txHash
string
required
​
confirmations
integer<int32>
required