From a920ba0088fd7df9a0e01d9e6bc0288000fbc1c8 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 27 Feb 2026 17:36:20 +0000 Subject: [PATCH 1/4] Clarify request signing requirement for crypto withdrawals Generated-By: mintlify-agent --- guides/developer/request-signing.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/developer/request-signing.mdx b/guides/developer/request-signing.mdx index 0ead3cfb..0d988364 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. While other authenticated endpoints work without request signing, crypto withdrawals require this additional security layer to protect your funds. 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. 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_. From 300c2f02940d1ec4782b5796bc37e764a0616fdf Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 27 Feb 2026 17:38:15 +0000 Subject: [PATCH 2/4] Fix wording: clarify crypto withdrawals fail until backend configured Generated-By: mintlify-agent --- guides/developer/request-signing.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/developer/request-signing.mdx b/guides/developer/request-signing.mdx index 0d988364..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 before you can use the [Create Crypto Withdrawal](/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal) endpoint. While other authenticated endpoints work without request signing, crypto withdrawals require this additional security layer to protect your funds. Contact [Support](https://support.paxos.com) to enable request signing for your account. +> 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 before you can use the [Create Crypto Withdrawal](/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal) endpoint. Contact [Support](https://support.paxos.com) to enable request signing for your account. +> 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_. From 09dffb6d4eabf1b4bebf13724749294cecfae6d7 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 27 Feb 2026 17:39:51 +0000 Subject: [PATCH 3/4] Add request signing note to Create Crypto Withdrawal endpoint Generated-By: mintlify-agent --- .../endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx b/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx index 4a27e33a..7776bde5 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 --- + +This endpoint requires [request signing](/guides/developer/request-signing) to be enabled by Paxos. 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. + + ```bash OAuth Scope transfer:write_crypto_withdrawal ``` From 3f4cbd23c4997ba8971d30ac89f2f84f51476712 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 27 Feb 2026 17:41:19 +0000 Subject: [PATCH 4/4] Fix wording: clarify request signing conditional behavior Generated-By: mintlify-agent --- .../endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx b/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx index 7776bde5..288f2c17 100644 --- a/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx +++ b/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal.mdx @@ -3,7 +3,7 @@ openapi: post /transfer/crypto-withdrawals --- -This endpoint requires [request signing](/guides/developer/request-signing) to be enabled by Paxos. 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. +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