API template library

Simulate the DocuSign ID Evidence API

A WireMock simulation of DocuSign's REST API — covering the identity verification event log recorded for an envelope recipient and the ID document images captured during verification.

Vendor
DocuSign
Functionality
ID verification events and images
Spec version
1.0.0
Endpoints
2
Stubs
12
Protocol
REST
Validation
AI-validated Before publication, an AI agent exercised these endpoints against the real DocuSign API through WireMock's recording proxy, and the recorded traffic was used to verify each stub's request and response shapes.

Live sandbox · no signup, no API key

DocuSign ID Evidence API

A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.

Base URL
https://k7jko9.wiremockapi.cloud

GET Omar Haddad's ID verification events

curl -s -X GET 'https://k7jko9.wiremockapi.cloud/api/v1/events/person/f1a3c5e7-2b4d-4f6a-8c9e-0d2f4b6a8c13.json' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

GET Lucia Romero's events, first page, without image links

curl -s -X GET 'https://k7jko9.wiremockapi.cloud/api/v1/events/person/ec302470-6b1d-4c7e-807f-86fcd4550656.json?include_media=false&page_size=2' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

GET Download the front image of his licence (base64 PNG)

curl -s -X GET 'https://k7jko9.wiremockapi.cloud/api/v1/events/person/f1a3c5e7-2b4d-4f6a-8c9e-0d2f4b6a8c13/5d7f9b1c-3e5a-4c7e-9f1b-4a6c8e0d2f73/media/a4c6e8f0-1b3d-4e5f-9a7c-2e4f6a8c0b51' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'
Method Path Summary
GET /api/v1/events/{entityType}/{entityId}.{format} Returns a list of events for a specific entity.
GET /api/v1/events/{entityType}/{entityId}/{eventId}/media/{mediaId} Gets the media item related to a specific event.

Unauthenticated WireMock Cloud demo sandbox for DocuSign — not an official DocuSign sandbox, and it returns simulated example data only.

What's inside the ID Evidence template

When a signer passes DocuSign ID Verification, the checks leave an evidence trail, and this API reads it back by the recipient's recipientIdGuid. Two recipients are on file. Lucia Romero verified with a passport and Omar Haddad with a US driver's licence; each log runs from envelope sent, through the image capture event, to a photo ID success that records the document type, issuing country and parsed name parts. The capture event lists absolute URLs for the front image and, for the licence, the back, and following one returns the picture as base64 PNG.

  • Event log — a recipient's events oldest first, with date-range filters and page_index and page_size paging
  • Verification outcome — the photo ID success event with ID type, issuing country, selected country and name components
  • Captured images — front and back ID images, linked from the capture event and returned as base64
  • Error contract — the spec's error, error_description and reference_id body on every failure

DocuSign ID Evidence mock API FAQ

The events call answers 404 with proof_service_proof_file_not_exists, the code a real account returns when no evidence is stored. That makes it straightforward to test the branch where a signer used a different authentication method.

person is the only entity type; anything else answers 400 invalid_request_parameter_value. The format suffix accepts .json and .pdf, and others such as .xml answer 406 requested_format_mismatch. A .pdf request returns the same JSON as .json, because the spec declares no PDF response body.

Yes. include_media=false drops the copy_of_id fields from the capture event, which keeps a log export small. Paging uses page_index from zero and page_size; asking for two of Lucia's three events reports totalItems 3 across two pages.

Lucia Romero appears in both. The Trust Records template holds the trust service provider's packaged evidence for her, a report PDF and signature evidence, while this API holds the raw verification events. The evidence is fixed, the token is never checked, and requests without an Authorization header answer 401.

Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.