Enable RFQ access

Enables RFQ access for the authenticated account.

Call this operation once before using the RFQ API. It has no request body and only initializes the account associated with the Bearer token. The operation is idempotent, so calling it again safely returns the current enabled state.

Enabling an account for the first time requires a Bearer token issued to the account’s main key; a token obtained with a subkey is rejected with 403. Once RFQ access is enabled, any token for the account, including a subkey token, receives the current enabled state.

A successful response has status ENABLED and identifies the account and delegated RFQ trading public key. If that delegated key was revoked on the account, RFQ access is disabled until the operation is called again with a main-key token: that call issues a new delegated key, leaves the revoked one revoked, and returns the new public key. A subkey token is rejected with 403 until then. If the new key it would enable is itself already revoked, the operation returns 409 with error SUBKEY_REVOKED and RFQ access stays disabled.

The delegated key counts toward the account’s subkey limit. If the account already holds the maximum number of subkeys when a new delegated key is needed, the operation returns 400 with error TOKEN_LIMIT_REACHED, the same error as subkey registration, and RFQ access stays disabled. Revoke a subkey, then call the operation again with a main-key token.

If the RFQ venue refuses to enable the account, the operation returns 400 with error REQUEST_NOT_ALLOWED and the venue’s reason as the message, and RFQ access stays disabled. Calling the operation again does not change that outcome.