Developer guides index
---
title: Developer guides index
description: Full index of Atlas API, integration, OAuth, MCP, and competitor-mapping developer guides.
date: 2026-06-22
updated: 2026-06-22
---
New to Atlas? Start at Getting started, then return here for API depth.
Every Atlas developer guide in one place. Start with E-signature API for the REST quickstart.
Atlas API
- Bulk Send API E-Sign
- Contract Signing API
- Create Envelope API
- Decline Envelope API
- Document Signing API
- E-Sign API
- E-Sign API Curl Example
- E-Sign API For Startups
- E-Sign API Openapi Spec
- E-Sign API Python Example
- E-Sign API Typescript SDK
- E-Sign SDK
- E-Sign Webhook
- E-signature API
- Embedded Esignature API
- Envelope API
- Esignature Template API
- Extract Contract Data API
- Field detection
- Idempotent Envelope Create API
- Legal intake and signing
- Multipart Upload E-Sign API
- Openapi Envelope Schema
- Platform E-Sign API
- Remind Signer API
- Repeat Contract Send API
- Send Contract API
- Sequential signing
- Sequential Signing API
- Sign PDF API
- Signature API
- Signing Status API
- Template Signing API
- Void Envelope API
OAuth and auth
MCP and agents
- Chatgpt E-Sign integration
- Claude E-Sign integration
- Codex CLI e-sign integration
- MCP electronic signatures
Integrations
- Airtable e-sign trigger
- DocuSign Google Sheets integration
- DocuSign Integration with Salesforce
- DocuSign SharePoint Integration
- E-Sign Salesforce integration
- GitHub Action contract signing
- Google Forms DocuSign integration
- Google Forms e-sign API
- HubSpot document signing
- HubSpot e-sign integration
- Make.com envelope signing with Atlas
- Microsoft Teams contract signing bot
- n8n Atlas e-sign workflow
- n8n DocuSign integration
- n8n e-sign
- Nintex E-Sign integration
- Notion contract signing integration
- Pipedrive DocuSign integration
- Pulumi e-sign integration
- Salesforce e-sign API
- Salesforce e-sign with Atlas
- Slack contract signing with the Atlas API
- Stripe webhook when a contract is signed
- Vercel e-sign integration
- your database e-sign webhook pipeline
- Zapier e-sign
- Zapier e-sign integration with Atlas
DocuSign mapping
- DocuSign Admin API
- Docusign API Create Envelope
- DocuSign API Documentation
- DocuSign API limits
- Docusign API Pricing
- Docusign API Status
- DocuSign CLM API
- DocuSign create envelope API
- DocuSign Integration Key
- DocuSign Monitor API
- DocuSign REST API
- Docusign SDK
- DocuSign template API
- Docusign Webhook
Competitor APIs
- Adobe Acrobat Sign API
- Adobe Sign API
- Adobe Sign API Alternative
- Adobe Sign API Documentation
- Adobe Sign API pricing
- Adobe Sign Integration
- Adobe Sign REST API
- Boldsign API
- Box Sign API
- Dropbox Sign API
- Hellosign API
- Hellosign API Pricing
- Hellosign Template API
- Migrate From Docusign API
- Pandadoc API
- Pandadoc API Alternative
- Pandadoc API Pricing
- PandaDoc Dropbox integration
- PandaDoc Integration
- Signnow API
- Signnow API Pricing
- Signwell API
More guides
Next steps
- Documentation hub
- Getting started
- Send from ChatGPT
- Branding
- API reference
- MCP getting started
- Platform overview
- Teams and permissions
- Invites and roles
- MCP orgs
- SAML SSO
- Field detection
- Sequential signing
How to pick a guide
Start with E-signature API if you want one HTTP flow from upload to webhook. Use Signature API when you already know Atlas routes and need a route map. Pick Sequential signing when legal cares about signer order, and Field detection when your PDFs vary and you want review before send.
Integration guides under Zapier, n8n, HubSpot, and Salesforce assume you will keep Atlas as the signing backend while CRM or ops tools trigger sends. DocuSign mapping guides translate incumbent envelope concepts to Atlas routes so migrations do not stall on naming differences.
Agent teams should read MCP electronic signatures after the REST quickstart so tool calls and webhooks stay aligned. If you are comparing vendors before you wire code, pair this index with /compare.
Most integration failures are auth or webhook shape mismatches, not missing features. When in doubt, prototype with E-signature API, then branch into CRM-specific guides once the first envelope completes end to end.
FAQ
Which guide should I read first?
E-signature API covers create, review, send, and webhook in one path.
Where are MCP setup docs?
See MCP getting started and MCP electronic signatures.
Do guides cover PDF and DOCX?
Yes. Upload guides and API create docs accept both formats; review and sign always use PDF.
Where is the full guide list?
You are on it. Bookmark /docs/guides or start from the documentation hub.