API template library

Simulate the DocuSign Monitor API

A WireMock simulation of DocuSign's REST API — covering the organization's security event stream with cursor-based polling, covering logins, envelope activity, permission changes and account setting changes.

Vendor
DocuSign
Functionality
Security event stream with cursor paging
Spec version
1.0.0
Endpoints
1
Stubs
5
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 Monitor API

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

Base URL
https://ldqvlj.wiremockapi.cloud

GET Read the first five security events

curl -s -X GET 'https://ldqvlj.wiremockapi.cloud/v1/organizations/f4c8e1d2-6a3b-4c5d-9e7f-1a2b3c4d5e6f/stream?limit=5' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

GET Poll from the end of the feed (empty page, same endCursor)

curl -s -X GET 'https://ldqvlj.wiremockapi.cloud/v1/organizations/f4c8e1d2-6a3b-4c5d-9e7f-1a2b3c4d5e6f/stream?cursor=aa_638982144000000000_638982143400000000_18' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'
Method Path Summary
GET /v1/organizations/{organizationId}/stream Gets customer event data for an organization.

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

What's inside the Monitor template

Monitor feeds DocuSign activity into a SIEM or security dashboard through one endpoint, an event stream read with a cursor. Lucky Shrub Holdings has 18 events, timed relative to the request so they always fall inside the default seven-day window. They are arranged to trip the alerts teams usually write: identity verification switched off on the account, a user promoted to administrator, six failed logins from Berlin through a VPN proxy followed by a success, then three envelope downloads minutes apart. Each row carries the parsed user agent, IP geolocation, proxy fields and an event-specific data object.

  • Authentication events — successful and failed logins with browser, OS, location and proxy details
  • Envelope activity — sent through the API with an integration key, voided with a reason, and downloaded
  • Administrative changes — an account setting disabled and a permission profile change naming the affected user
  • Other products — a document deletion from CLM and a workflow instance started in Maestro
  • Cursor paging — ISO 8601 or opaque cursors, a limit parameter, endCursor and rate-limit headers

DocuSign Monitor mock API FAQ

Pass the endCursor from your last response. Once the feed is exhausted, the call returns an empty resultData together with the same endCursor you sent, which is the stop condition DocuSign's polling guidance relies on. Store that cursor and poll again later.

An ISO 8601 date-time to start from a point in time, or the opaque aa_… value from a previous endCursor. Leave it off to read the last seven days. Anything else, such as a plain word, answers 400 INVALID_REQUEST_PARAMETER explaining the two accepted forms.

No. The 18 events are fixed, and because their timestamps track the request time they look recent on every run, which suits alert-rule tests in CI. Activity in the other DocuSign templates doesn't flow into this stream. Organizations other than Lucky Shrub Holdings return an empty feed.

Neither. Responses include X-RateLimit-Remaining and X-RateLimit-Reset headers so header parsing can be tested, but no 429 is ever returned. Any Bearer token works, and a request with no Authorization header answers 401 AUTHORIZATION_INVALID_TOKEN.

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