Adobe Acrobat Sign vs BoldSign

Adobe Acrobat Sign 10

The newest dated entry in the API release notes is November 2025, more than 180 days before this check, and the developer guide was last updated on 17 December 2025 (0). No dated API entries fall in the last 90 days (0). Closed service with release notes, a developer forum link and support. The GitHub repository's last commit is still 14 May 2026 (a redirect script), with the release notes page's content last changed on 30 October 2025 (its "Last update" line; a 22 January 2026 commit only added a redirect script), re-read from a clone on 4 November; its nine open issues are per the 8 October check. We didn't test a support channel (5 of 15). Adobe's SDK page says its SDKs are obsolete, and a Postman workspace is the suggested replacement (3 of 15). The SDK code hasn't changed since August 2022 and the repository has no CI workflow (2 of 10). Product release notes on helpx.adobe.com answered 403 and went unread, so newer product changes may exist. The developer guide and release notes on developer.adobe.com are per the 8 October check, not re-read on 4 November. 0+0+5+3+2 = 10.

BoldSign 78

Read as a closed service. The API changelog's newest entry is 16 October 2026, and the PHP SDK repository was pushed the same day, Java and Python on 13 October (30). Changelog entries on 13 August, 19 August, 7 September, 23 September, 8 October and 16 October 2026 (20). Support site, knowledge base and support@boldsign.com, with a public changelog. GitHub issues on the SDK repositories were not read (8 of 15). Five official SDKs, Node at 3.3.4 since August 2026. The hosted MCP server is not in the official MCP registry (15). The Node SDK clone shows no CI workflow and the deprecated MCP package stopped at 0.0.5 (5 of 10). 30 + 20 + 8 + 15 + 5 = 78.

Adobe Acrobat Sign 54

Graded on the REST v6 API. The live reference is a Swagger UI on secure.na1.adobesign.com, whose robots.txt disallows crawlers, so we didn't read it. The only downloadable contract found is a set of Swagger 1.2 files from August 2018 with 92 operations, and Adobe calls the SDKs built from it obsolete (12 of 25). developer.adobe.com/llms.txt returns 404 (0). The developer guide and a best practices page of 17 December 2025 state required scopes, valid state transitions and good and bad call patterns for each main endpoint (12 of 20). The 2018 files mark 231 of 489 parameters required and hold 99 enums (9 of 15). The guide has request and response examples and named error codes, with per-endpoint error lists in the reference we didn't read (10 of 15). The API is versioned in the path, and the release notes are dated by month, most recently November 2025 (11 of 15). Per the 8 October check, not re-read on 4 November, since Adobe's hosts are paused for this run.

BoldSign 85

A public Swagger file, OpenAPI 3.0.4, at api.boldsign.com/swagger/v1/swagger.json with 87 operations and two security schemes, X-API-KEY and Bearer, which the docs say generated the C# SDK (25). developers.boldsign.com serves llms.txt and a Markdown twin of every page (10). Every operation has a summary, but 64 of 87 are under 40 characters in the file, and the purpose and conditions of each call sit in the docs pages instead. The MCP docs say which tools read and which act (12 of 20). 186 enums and required fields in the schemas, with page and pageSize on lists (12 of 15). The Swagger file carries no examples. The docs pages carry curl and five SDK examples per call, and the troubleshooting page documents 400, 401, 402, 403, 404, 417 and 422 with causes and fixes, while the file documents 401 everywhere and 403, 422 and 400 on many operations (11 of 15). v1 in the path with v1-beta for previews, and a changelog dated from 20 April 2021 to 16 October 2026 that labels breaking changes (15). 25 + 10 + 12 + 12 + 11 + 15 = 85.

Adobe Acrobat Sign 61

Graded as a hosted API. status.adobe.com is Adobe's status page and the Unified SLA names it for outage notices, but the page is drawn by script and no Acrobat Sign component or component history was confirmed, so the line is scored as adobe-pdf-extract's is (15 of 20). No incident history could be read, so the last 90 days are scored as unreadable (5). Numbers are published for /search (1,000 a minute, 2,500 an hour, 7,200 a day) and for identical GET calls (three a minute on Global, Enterprise and Developer tiers). Per-endpoint limits depend on the plan and aren't published (9 of 15). 429 responses carry Retry-After and a retryAfter field, the guide asks for exponential backoff, and If-Match ETags stop stale updates. No idempotency key was found for POST /agreements (12 of 15). The Unified SLA of 3 August 2026 commits to 99.9 per cent for Acrobat Sign Solutions for Enterprise, with credits of 5 to 25 per cent (10). REST v6 is generally available (10). Per the 8 October check, not re-read on 4 November, since Adobe's hosts are paused for this run. 15+5+9+12+10+10 = 61.

BoldSign 84

Read with the hosted lines and scored on the REST API v1, the surface the SDKs and the hosted MCP server call. status.boldsign.com on Atlassian Statuspage has Web App and API components for Global, Europe, Canada and Australia plus Docs, with 90-day uptime and an incident history (20). The history feed, read on 3 November 2026, lists four one-hour scheduled maintenances between 19 and 27 September and no incident after a 20-minute partial disruption on 21 July 2026, so the 90 days from 5 August are clean (30). Rate limits are published per account, 2,000 requests an hour live and 50 an hour in the sandbox (15). The rate-limit page says 429 is returned with messages and usage is tracked in response headers, and the guide recommends webhooks over polling. No Retry-After is documented and there are no idempotency keys (6 of 15). No SLA document was found. security.txt advertises a 99.999 per cent uptime SLA, the terms disclaim uninterrupted service and refer to a support SLA available on request (3 of 10). v1 is the stable version with beta endpoints under v1-beta (10). 20 + 30 + 15 + 6 + 3 + 10 = 84.

Adobe Acrobat Sign 25

Read with the hosted rubric. No x402, MPP or L402 found (0). Acrobat team plan prices are public, but the pricing page doesn't say they include API access, and Acrobat Sign Solutions is by quote with no per-transaction price. We scored between plan-only and contact sales (5). The Developer Edition is free with API access. The sign-up page says no commitments and doesn't mention a card, and we didn't run the form (20). A person must create an Adobe ID, register an application and approve OAuth in a browser (0). Per the 8 October check, not re-read on 4 November, since Adobe's hosts are paused for this run.

BoldSign 40

Read with the hosted rubric. No x402, MPP or L402 (0). The Enterprise API plan is public at $30 a month with 40 envelopes and $0.75 per additional envelope, and add-ons are priced per unit (20). The free sandbox gives full API access with no credit card, and the 30-day trial also needs no card per the pricing page (20). A person signs up in a browser and mints the key or registers the OAuth app in the web app (0). 0 + 20 + 20 + 0 = 40.

Adobe Acrobat Sign 55

List calls take pageSize and return ETags for 304 responses. No field selection was found (13 of 25). Cursor pagination with page.nextCursor, a /search endpoint and a 500-agreement page cap (15 of 20). Errors are JSON with a stable code and message, such as INVALID_API_ACCESS_POINT, THROTTLING_TOO_MANY_REQUESTS and RESOURCE_MODIFIED (15 of 20). No idempotency key. If-Match protects updates and a DRAFT state lets a caller build an agreement before sending (8 of 20). A caller must first discover the account's shard, sending a file takes an upload call and then an agreement call, and Adobe marks every SDK deprecated (4 of 15). Per the 8 October check, not re-read on 4 November, since Adobe's hosts are paused for this run.

BoldSign 62

List calls take Page and PageSize and document properties return the full object; no field selection was found. The hosted MCP server has 14 compact tools, but the REST API is the graded surface (14 of 25). Page and PageSize on document, template, contact, user and team lists, with search, status, date, label and team filters on documents (16 of 20). The troubleshooting page gives a cause and a fix per status code, 401 covers a region mismatch, and 422 carries validation detail (14 of 20). No idempotency keys. Draft send and the sandbox make trial calls safe, and the MCP docs ask for a human confirmation before send, reminder and revoke, but the tools' annotations couldn't be read (5 of 20). A send needs files or a template, a title and signers with fields, and the SDKs cover .NET, Node, Python, Java and PHP (13 of 15). 14 + 16 + 14 + 5 + 13 = 62.

Adobe Acrobat Sign 71

Closed service under the Adobe General Terms of Use of 3 October 2025 and the Acrobat Sign product terms of May 2023. The documentation repository is MIT (15). The privacy policy of 24 October 2025 keeps most personal information while the user is active and contract records for ten years. The product terms store customer content for the licence term, and the General Terms say content isn't used to train generative AI models, with content analytics on by default and an opt-out. The data processing agreement wasn't read (18 of 30). v5 and SOAP are marked deprecated without an end date. Classic webhooks were retired on a dated schedule in 2023, and the product terms promise only reasonable effort to give notice of changes (8 of 20). The sub-processor list of 28 September 2026 names each company with its locations, with OpenAI and Google among them (18 of 20). Per the 8 October check, not re-read on 4 November, since Adobe's hosts are paused for this run.

BoldSign 77

Closed service under Terms of Use effective February 2025 that name Syncfusion, Inc. and North Carolina law. The SDKs and the deprecated MCP package are MIT (17 of 30). The privacy policy (July 2026) keeps personal data as long as necessary with no number, the terms keep signed documents and audit trails at least three years and schedule inactive accounts for deletion after six months, sandbox documents go after 14 days, and the terms say customer data is used for nothing but performing the agreement. A subprocessor list is linked and no DPA was found on the pages read (20 of 30). No deprecation policy. The terms let Syncfusion modify or discontinue BoldSign at its discretion, and the changelog labels breaking changes without a notice period (6 of 20). The privacy policy links the subprocessor list, and the security page names Google Cloud and Azure regions in US East, the EU, Canada and Australia (16 of 20). 17 + 20 + 6 + 16 = 59.