API Endpoints
List HTTP methods, URL patterns, parameter descriptions, expected response codes, and sample payloads for each endpoint.
A well-structured Business Services Salesforce API Document reduces integration errors, shortens developer onboarding, and provides an auditable record of data flows and signing points. It supports compliance with ESIGN and UETA by documenting where electronic signatures occur and how records are retained for legal and regulatory review.
Typical readers include technical implementers, compliance officers, and downstream business users who rely on signed documents or automated approvals.
Each group uses the document differently: developers need request/response examples; legal needs signature capture and retention detail; operations track delivery and errors.
| Field | Configuration |
|---|---|
| Trigger Event | Opportunity close, record update, or custom Apex event |
| Signer Order | Define sequential or parallel signing order |
| Notification Method | Email invite or one-time signing link |
| Failure Handling | Retry logic, alerts, and logging destinations |
The Business Services Salesforce API Document should specify platform dependencies, supported file formats, and integration points.
Document versioning and API change notifications are essential to avoid breaking downstream automations; include contact and rollback procedures.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Available | Available | Available | Available |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
List HTTP methods, URL patterns, parameter descriptions, expected response codes, and sample payloads for each endpoint.
Describe authentication flows, token refresh behavior, required scopes, and error responses for expired or insufficient credentials.
Provide exact Salesforce field API names, data types, formatting rules, and conversion rules for signed document metadata.
Specify event types, retry policies, authentication, and example callback payloads for signed/completed events.
Define required audit trail fields, retention policies, and where signed PDFs and certificates of completion are stored.
Document rate limits, throttling behavior, expected uptime, and escalation contacts for production incidents.
Xerox integrated signing into its ERP workflows to reduce manual steps and centralize approvals.
A real estate operator moved lease signings online to avoid in-person delays.
| Criteria | Electronic signature | Digital signature |
|---|---|---|
| Legal status | acceptable under esign/ueta | acceptable and stronger evidentiary value |
| Technology | any electronic process | pki, x.509 certificate |
| Non-repudiation | audit trail evidence | cryptographic non-repudiation |
| Common use cases | contracts, approvals | fda-regulated, high-assurance |