If present, filters transaction requests by the specified wallet types

If provided, transaction requests with the specified intent types will be excluded.

If provided, only transaction requests of the specified state will be returned.

• canceled: Canceled by a wallet spender before approval or sending.
• delivered: Inserted into the send queue (or rejected by BitGo through circuit breakers). This state is only used with apiVersion "full".
• failed : Catch-all state indicating an unrecoverable failure (such as a duplicate key error when creating a transfer).
• initialized: First state when a transaction request is created (before any policy evaluation occurs).
• pendingApproval: Triggered a policy that requires approval to proceed.
• pendingDelivery: Requires further action to proceed (such as pending signature, or accepting/rejecting due to triggering a circuit breaker). This state is only used with apiVersion "full".
• pendingUserCommitment: Ready to receive your user commitments. This state is only used with apiVersion "lite" and EdDSA assets with commitment signing states.
• pendingUserGShare: Ready to receive your gShare.
• pendingUserRShare: Ready to receive your rShare.
• pendingUserSignature: Ready to receive your user signature (get the unsigned transaction from BitGo and sign it). This state is only used with apiVersion "lite" and EdDSA assets without commitment signing states.
• readyToSend: Ready send (share combination is complete).
• rejected: Rejected by an approver.
• signed: All transactions in the transaction request were signed. All future updates will be in the transfer document.

If present, filters transaction requests by wallet permissions. If not present will default to view permissions