diff --git a/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx b/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx index 4a27e33a..288f2c17 100644 --- a/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx +++ b/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx @@ -2,6 +2,10 @@ openapi: post /transfer/crypto-withdrawals --- + +If you have [request signing](/guides/developer/request-signing) enabled, this endpoint will not work until Paxos configures it on the backend. Contact [Support](https://support.paxos.com) to complete the setup. + + ```bash OAuth Scope transfer:write_crypto_withdrawal ``` diff --git a/guides/developer/request-signing.mdx b/guides/developer/request-signing.mdx index 0ead3cfb..7ebb8f08 100644 --- a/guides/developer/request-signing.mdx +++ b/guides/developer/request-signing.mdx @@ -6,7 +6,7 @@ description: Use JWS to add an additional layer of security to every request. Request signing adds an additional layer of security to every request you send to Paxos, and can help protect your account should your Paxos API Client ID and Secret become compromised. Once request signing is enabled on your account, Paxos rejects all unsigned requests to authenticated endpoints. -> Request signing must be activated by Paxos. Contact [Support](https://support.paxos.com) to get started. +> Request signing must be activated by Paxos before you can use the [Create Crypto Withdrawal](/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal) endpoint. All other authenticated endpoints will work with request signing, but crypto withdrawals will fail until Paxos configures this on the backend. Contact [Support](https://support.paxos.com) to enable request signing for your account. Signed requests use your own private key, similar to [mTLS](https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/) or [SSH](https://www.ssh.com/academy/ssh/public-key-authentication) public authentication, and then attach the signature to the request as the `Paxos-Signature HTTP header`, using the JSON Web Signature (JWS) format. @@ -46,7 +46,7 @@ Go to **Admin > API** in either [Sandbox][admin-api-sandbox] or [Production][ad Go to ** Admin > API** in either [Sandbox](https://dashboard.sandbox.paxos.com/admin/api) or [Production](https://dashboard.paxos.com/admin/api) and find the **API Credentials** that require request signing. -> Request signing must be activated by Paxos. Contact [Support](https://support.paxos.com) to get started. +> Request signing must be activated by Paxos before you can use the [Create Crypto Withdrawal](/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal) endpoint. All other authenticated endpoints will work with request signing, but crypto withdrawals will fail until Paxos configures this on the backend. Contact [Support](https://support.paxos.com) to enable request signing for your account. Scroll down and use **Edit API Credentials** to make changes. Switch **Request Signing** to open the edit dialogue and add your _Public Key_.