Envelope Void Api with Atlas

You do not need a giant CLM suite to collect signatures. This page covers envelope void api with Atlas.

> Share: "Upload, review, send. That is the loop for envelope void api."

What to do

1. Upload PDF or DOCX at /signup or via POST /api/envelope.
2. Open review_url and confirm fields and signers.
3. Click Send when ready.
4. Use webhooks or status checks to know when signing finishes.

More detail lives at /docs/guides/e-signature-api.

Create an envelope

curl -X POST https://atlaswork.ai/api/envelope \
  -H "Authorization: Bearer $ATLAS_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: create-envelopevoidapi" \
  -d '{
    "document_url": "https://example.com/agreement.pdf",
    "parties": [{"email": "signer@example.com", "name": "Jane Signer", "role": "Customer"}],
    "webhook_url": "https://your-app.com/atlas/webhook"
  }'

Open the review_url in the response. Confirm fields and parties, then click Send.

Retry safety

Send an Idempotency-Key header when you create or send an envelope. If your job retries the same request, Atlas returns the first result instead of charging twice.

MCP tools add a key for you when you forget. REST jobs should set one on purpose.

Webhooks

Set webhook_url when you create the envelope. Atlas POSTs events when something changes. Check the X-Atlas-Signature header with your API key before you update your app.

Common events: envelope.sent, envelope.signed, envelope.declined, envelope.voided.

See platform webhooks for debugging tips.

Errors you will see

402 means you are out of send credits. 409 means fields are still processing or someone else edited the envelope. Save envelope_id on every create so support can trace issues.

What to do next

Try five free sends at /signup. Read /docs/guides/e-signature-api for the full guide.

Common mistakes

Teams new to envelope void api often send before field detection finishes. Wait until fields_status is ready. If you hit 409, open review_url and check the banner.

Another miss: sharing a bare /sign/{id} link on multi-party deals. Each signer needs their token in the URL so they only see their fields.

Do not store API keys in frontend code or chat bot configs. Create envelopes from a server you control.

Staging checklist

Run one envelope to your own email before production traffic. Confirm webhook delivery, signed PDF download, and credit decrement match what finance expects.

Log create responses in structured JSON. When a signer says "I never got email," envelope ID finds the row faster than subject search.

If you use agents, document three approved prompts: create send, check status, remind signer. Wild prompts in live deal threads cause wrong-party sends.

When Atlas is the wrong tool

Atlas targets builders, agents, and usage-priced sends. If legal mandated DocuSign for every department, keep DocuSign for those flows and use Atlas where code creates the envelope.

If you need clickwrap on a marketing site with no review step, compare specialized clickwrap vendors. Atlas assumes a PDF or DOCX artifact and sequential signing.

Practical tips

Save envelope_id beside your CRM or ticket ID. Use metadata.client_reference_id on create so you can match webhooks back to your records.

Alert on 402 (out of credits) and 409 (fields still processing) in production jobs.

Train support to ask for envelope ID first. Subject lines lie.

Review credit burn monthly if you run seasonal bulk sends.

FAQ

Does Atlas accept PDF and DOCX?

Yes. Upload either format when you create an envelope. DOCX files become PDF before anyone signs.

How do I sign in?

Use a Bearer API key from your dashboard settings. MCP connectors in ChatGPT and Claude use OAuth instead.

When do credits get used?

One credit per send, not per upload. You get five free sends when you sign up.

Where should I start?

/docs and API reference.

Related reading

• Documentation
• E-signature API guide
• MCP electronic signatures