Source
Signer identification — found from sitemap — Legalesign
Checked for Legalesign on 3 Nov 2026
- Page
- https://legalesign.com/articles/esignature-api/API-verification/
- Checked
- 3 Nov 2026, 15:52 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:7235a6b4e44f0e9c3dc692f26c45657591ead4104151a28305d88707b0de410d
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
API key required Report an error
“To start using the API, login to the Developer Portal and create an API key.”
-
Sandbox throttle Report an error
“A throttle limit of 100 API calls per hour”
-
Sandbox banner Report an error
“An 'API Test' banner displayed along the top of the signing page.”
-
Plugin setup Report an error
“If you intend to use a ready-to-go plugin (e.g. Salesforce or Voyager Infinity) contact support to let us know.”
-
Production mode Report an error
“Contact Support to move out of sandbox, add multiple teams, or identify specific dev teams to exclude from any future billing.”
-
Webhooks legacy Report an error
“About Legacy Webhooks”
-
Zapier Report an error
“Zapier”
-
Postman Report an error
“Using Postman”
-
AI mcp Report an error
“AI Tools (MCP)”
Scores citing this record
- The Data Protection Officer Integrations & API
- The Data Protection Officer Pricing transparency
- The HR Operations Lead Integrations & API
- The HR Operations Lead Pricing transparency
- The Integration Engineer Integrations & API
- The Legal Counsel Integrations & API
- The Revenue Operations Lead Integrations & API
- The Revenue Operations Lead Pricing transparency
- The Skeptic Signer identification
- The Skeptic Integrations & API