Every example on this page — endpoints, fields, code and responses — is a demonstration for illustration only, and is not a binding specification, an offer or a commitment to availability or behavior. Actual API access is subject to opening an account, obtaining an API key, service configuration and the terms of use.
An API for signatures, contracts and user consents
Connect IsraeliSign to a website, app, CRM or SaaS system, and create a flow where a client or user receives a document, approves terms, signs — and your system gets status and records back.
- Create flow
- Send link
- Webhook after signing
- Return to system
How it works
Signing becomes part of your flow — not an external step the client has to leave for. The system creates a request, returns a signing link, and updates you when the document is opened, approved and signed.
- Your system
Your system creates a signature request
Demo only# Create a signature request curl -X POST https://api.israelisign.com/v1/envelopes \ -H "Authorization: Bearer DEMO_KEY" \ -d '{ "name": "Service Agreement", "documents": [{ "file_url": "https://example.com/agreement.pdf" }], "signers": [{ "name": "Israel Israeli", "email": "israel@example.com" }], "webhook_url": "https://yourapp.com/webhooks" }' - IsraeliSign
IsraeliSign returns an envelope_id and signing_url
Demo only{ "envelope_id": "env_demo_123456", "status": "created", "signing_url": "https://app.israelisign.com/sign/env_demo_123456" } - The client
The client opens the link, approves and signs
- IsraeliSign
IsraeliSign sends a Webhook to your system
- The user
The user returns to your site or app
The examples are for illustration only and are not a binding specification. Actual API usage is subject to opening an account, obtaining an API key and configuring the service.
Two API tracks
One track for full documents and contracts, and a second for recording user consents on websites and apps.
Document Signing API
For documents, contracts, quotes and forms.
- Create a signing envelope
- Add signers and signing order
- Send a signing link
- Track status in real time
- Retrieve the signed document
- Webhooks for signing events
Consent API
For websites, apps and SaaS systems.
- Create a consent event
- Record the terms version
- Record language and time
- Record the user identifier
- Record marketing consent and preferences
- Webhooks after approval
How much does it cost?
The documents & signing API is included in the signing plans from ESSENTIAL up. Site consents and user approvals have a dedicated package. All prices are before VAT.
Document Signing API
Included in these plans
ESSENTIAL
Up to 80 signing processes per month
₪100 / month
GROWTH
Up to 150 signing processes per month
₪130 / month
PROFESSIONAL
Up to 250 signing processes per month
₪190 / month
Consent API
For website approvals, terms of use, privacy, cookies, marketing and policy updates
- Up to 5,000 API actions per month
- Terms-of-use approvals
- Privacy-policy approvals
- Cookie approvals
- Marketing and permission approvals
When to use the API
Anywhere you need an approval or signature as part of the process — you can embed it directly, without taking the client out of your system.
- Terms-of-use acceptance at signup
- Approval of an updated privacy policy
- Signing an engagement agreement
- Quote approval
- Signing as part of onboarding
- Approving a document from a customer area
- Embedding signing in a purchase flow
Want to embed signing inside your product?
Get an API key and make signing a natural part of your website, app or SaaS — with records and status for every document.
Every example on this page — endpoints, fields, code and responses — is a demonstration for illustration only, and is not a binding specification, an offer or a commitment to availability or behavior. Actual API access is subject to opening an account, obtaining an API key, service configuration and the terms of use. The validity of a signing process depends, among other things, on the document type, verification method, and applicable law. IsraeliSign is not legal advice.