Skip to content
E-signature

docusign.com

Test against the DocuSign eSignature API API

A hosted, stateful simulation shaped like the DocuSign eSignature API API. Writes persist, data moves on a schedule and every change can fire a signed webhook. Unofficial: not affiliated with docusign.com.

Operations
250
Start this simulation Vendor documentation
example request
curl https://api.slurry.io/s/your-docusign/restapi/v2.1/accounts/123 \
  -H "Authorization: Bearer slurry_sim_live_..."

Your simulation gets its own hostname, key and IP allow-list. Spec snapshot: version v2.1.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 250.

  • POST/v2.1/accounts
  • GET/v2.1/accounts/{accountId}
  • DELETE/v2.1/accounts/{accountId}
  • GET/v2.1/accounts/{accountId}/brands
  • POST/v2.1/accounts/{accountId}/brands
  • DELETE/v2.1/accounts/{accountId}/brands
  • GET/v2.1/accounts/{accountId}/brands/{brandId}
  • PUT/v2.1/accounts/{accountId}/brands/{brandId}
  • DELETE/v2.1/accounts/{accountId}/brands/{brandId}
  • GET/v2.1/accounts/{accountId}/brands/{brandId}/file
  • GET/v2.1/accounts/{accountId}/brands/{brandId}/logos/{logoType}
  • PUT/v2.1/accounts/{accountId}/brands/{brandId}/logos/{logoType}