Get the most from eSign 360
Short guides to the newer features: Word files, reusable links, in-person signing, Google Drive, Zapier and Make, API volume pricing and AI assistants.
In this guide
- Send a Word document
- Share one link that many people can sign
- Sign in person
- File signed documents to Google Drive
- Connect Zapier or Make
- API volume pricing
- Test and replay webhooks
- Emailed code and SMS code for signers
- Use an AI assistant
Send a Word document
You can upload a Word (.docx) file anywhere you can upload a PDF: in the web app, through the API and from Zapier or Make. eSign 360 converts it to a PDF when you upload it, then you place the fields as normal. The Word file itself is not kept, and the signed document is the PDF.
- Older
.docfiles are not accepted. Save them as.docxor PDF first. - Fonts that we do not have are replaced, which can move text between pages. For a layout you control exactly, export the PDF from Word and upload that.
- Documents with macros, embedded objects or links to outside pictures are refused with a message that says why. Save a copy without them.
- Check the converted pages before you send. Fields are placed on the PDF, not the Word file.
Share one link that many people can sign
A reusable signing link suits forms that many people complete: a waiver, an enrolment, a consent form, a volunteer agreement. Anyone with the link can open it, enter their details and sign. Each person gets their own copy of the document with its own audit trail, and nobody sees anyone else’s.
- Each completed copy is a normal document. It shows in your document list and counts as one document sent.
- You can turn a link off at any time. Copies already started can still be finished unless you cancel them.
- Through the API, list the copies from one link with
GET /documents?openLinkId=.
Sign in person
In-person signing is for when the signer is in the room with you: at a counter, on site or at a client’s office. You open the document on your phone, tablet or laptop and hand it to the signer. Their details and consent are recorded in the audit trail, along with the fact that it was signed in person on your device.
- The signer needs no email address or account.
- The certificate shows an
IN_PERSON_SIGNING_STARTEDevent for the signing session.
File signed documents to Google Drive
Connect your Google account in the Files settings and choose a folder and a rule. Signed documents are then filed to Drive for you, the same way they can be filed to OneDrive or SharePoint.
- eSign 360 asks for the narrow Drive permission. It can only see and change files and folders that it created itself, and cannot read anything else in your Drive.
- Disconnect any time in Files settings. Documents already filed stay in your Drive.
Connect Zapier or Make
The Zapier and Make connectors let you send a document, remind signers, cancel a document and find a document, and start a workflow when a signer opens, signs or declines or when a document is completed, expires or is cancelled. Both are submitted and going through each marketplace’s review, so they may not be listed yet.
- In the eSign 360 web app open Developers and create a credential. Use a sandbox credential while you build: no real emails go out and nothing is billed.
- In Zapier or Make, add eSign 360 and paste the Client ID and Client Secret.
- Pick a trigger or action. Triggers are instant, because the connector registers a webhook rather than checking on a timer.
- Switch to a live credential when you are ready.
Send document accepts a PDF or a Word file and places signature boxes for you. Each environment can have up to 10 active webhook endpoints, so for many Zaps use fewer triggers and filter inside the Zap.
API volume pricing
API plans have volume pricing, counted each calendar month in UTC. Each band is charged at its own rate, so sending more never costs more in total. At the standard rate of A$2.00 a document:
| Documents sent in the month | Price per document |
|---|---|
| 1 to 1,000 | A$2.00 |
| 1,001 to 5,000 | A$1.70 |
| 5,001 to 20,000 | A$1.40 |
| Over 20,000 | A$1.10 |
Prices exclude GST. Bands apply to API plans selected from 16 November 2026; earlier plans keep their flat rate until changed. See the API page, which links to the full API reference.
Test and replay webhooks
Check your webhook receiver without sending a document, and recover from an outage without waiting for new events. These work with the API for each environment (sandbox or live).
POST /webhooks/{id}/testqueues a test event (signer.signedunless you name another). It is signed and retried like a real event, and its body hasdata.test: trueand aDOC-TEST-document id. Up to 30 an hour per endpoint.GET /webhooks/{id}/deliverieslists the 50 most recent deliveries with their status and last response code.POST /webhooks/{id}/deliveries/{deliveryId}/redeliverputs a past delivery back in the queue with a fresh 24-hour retry window. It keeps the same event id, so a receiver that ignores repeated ids will treat it as a duplicate.
Verify each delivery with the X-P360-Signature header: t=<time>,v1=<HMAC-SHA256 of "<t>.<raw body>" using your endpoint secret>. Reply with any 2xx within 10 seconds.
Emailed code and SMS code for signers
There are two separate checks, and the API controls them separately.
- Emailed one-time code (
lockToSigner). On by default for any signer who cannot forward the request (canDelegate: false), so a forwarded email cannot be used by someone else. The signer sees “Verify your identity to continue” before consent. SendlockToSigner: falsewhen you add the signer to switch it off. It cannot be changed after the document is created. - SMS one-time code (
requiresOtp). Off unless you turn it on; switching it off does not remove the emailed code.
The certificate names a check only when the signer completed it. If no code was entered, it says the signer used the unique link only.
Use an AI assistant
Claude, ChatGPT and developer tools can prepare, send, track and remind through eSign 360. You confirm before anything is sent. If your assistant cannot read a file on your computer, it gives you a one-time upload link: open it, choose the PDF (up to 20 MB), then tell the assistant it is done. See AI assistants for the guides.