From e723ac979d07def6ce74c5ba05f5c19bb5fd2cc4 Mon Sep 17 00:00:00 2001 From: Yacine Kahlerras Date: Fri, 9 Oct 2026 12:26:40 +0100 Subject: [PATCH] fix(skill): create_signing_url never throws NotSignersTurn (TurboDocx/Docs#213) The API's only turn refusal is RecipientNotInTurn. Note that the SDK still catches NotSignersTurn for cross-SDK parity so generated code doesn't add handling for it. Co-Authored-By: Claude Opus 5.5 --- skills/turbodocx-sdk/references/python.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/turbodocx-sdk/references/python.md b/skills/turbodocx-sdk/references/python.md index 7980b1f..2c91606 100644 --- a/skills/turbodocx-sdk/references/python.md +++ b/skills/turbodocx-sdk/references/python.md @@ -494,7 +494,7 @@ Returns `documentId` plus `recipients`; each entry has `recipientId`, `name`, `e - `'pending'` — an earlier signer hasn't finished; `embedUrl` is `None`. Re-mint with `create_signing_url` once earlier signers complete. - `'completed'` — they already signed; `embedUrl` is `None`. -This is one underlying condition seen from both methods: `create_signing_url` **throws** `RecipientNotInTurn` / `NotSignersTurn` / `RecipientAlreadySigned`, while `create_embedded_signature` **catches exactly those codes** and degrades them to `pending` / `completed`. Any other error propagates. An SMS-OTP recipient with no `phone` (E.164) raises `PhoneRequiredForSmsOtp` before the send. +This is one underlying condition seen from both methods: `create_signing_url` **throws** `RecipientNotInTurn` / `RecipientAlreadySigned`, while `create_embedded_signature` **catches those codes** and degrades them to `pending` / `completed`. (The SDK also catches `NotSignersTurn` for cross-SDK parity; it is reserved and the current API never returns it, so don't write handling for it.) Any other error propagates. An SMS-OTP recipient with no `phone` (E.164) raises `PhoneRequiredForSmsOtp` before the send. ### The three identity modes