Integrate Contract Management Into Your Existing System — Without Replacing It
Your CRM, LOS, or ERP already works. You don't need to replace it with a contract management tool. Legal Cloud Bharat plugs into your existing system via REST API — create contracts, trigger signing workflows, and receive real-time status updates through webhooks. Your system stays in control.
How It Works — 4 Steps
The integration follows a simple request-process-notify-download cycle:
- Your App Calls the Integration API:Send a POST request with customer details, documents (PDF as Base64), and signer configuration. LCB creates a case folder, registers customers, and prepares the contract for signing.
- LCB Processes the Contract:The contract goes through the LCB platform — eStamping, approval workflow, and eSigning with all 7 signing methods. Your system doesn't need to manage any of this.
- Event API Fires a Webhook:When a signer signs, declines, or the contract completes, LCB sends a webhook POST to your registered URL with the event details. Configurable per event type.
- Your App Downloads the Signed Contract:Call the download endpoint with the document ID. Receive the signed PDF with audit trail — store it in your system, update your records, close the deal.
Integration API Endpoints
Base URL: /api/legalcloud. All endpoints require Bearer JWT authentication.
| Method | Endpoint | Purpose |
|---|---|---|
| POST | customer/registration | Create folder, register customers, upload documents, initiate signing |
| POST | document/signature/{folderId} | Create digital signing request (eSign or eStamping) |
| GET | download/{documentId}/documenttype/{type} | Download signed contract or eStamp certificate as PDF |
| GET | getbusinessplans | Retrieve available business plan types for folder creation |
| DELETE | delete/draft/{docBuilderId} | Delete a draft document before signing begins |
| POST | convert/tobase64 | Convert uploaded file to Base64 (100MB max) |
What You Send — Request Payload
A single API call creates the entire contract package:
- Business Plan:The type of deal/case (must match available plans in your LCB account).
- Folder Name:Name for the case folder — e.g., "Loan Agreement - ABC Corp".
- Unique Reference Number:Your system's unique ID for this contract — used for tracking and deduplication.
- Internal & External Signers:List of signers with name, email, phone, DOB, PAN card, role (internal or external), and signature mode.
- Documents:PDF files as Base64-encoded strings. Document name and file data per attachment.
- Request Type:eSign (1) for digital signatures or eStamping (2) for stamp paper + signatures.
Event API — Real-Time Webhooks
Configure which events trigger webhooks to your system. When a contract status changes, LCB sends a POST to your registered URL:
- Signed:A signer has signed the document. Payload includes signer email and document ID.
- Declined:A signer declined to sign. Your system can take corrective action.
- Reviewed:Document has been reviewed by a reviewer.
- Recalled:Contract was recalled by the drafter before completion.
- Completed:All signers have signed. Contract is fully executed and ready for download.
- Pending:Contract is pending signatures — sent to signers.
Webhook payload: Event name, Document ID, Drafter email, Event actioner email, timestamp. Your system receives this and decides what to do — download the contract, update CRM records, notify internal teams, or trigger the next business process.
Authentication
The API supports three authentication schemes:
- Bearer JWT:Primary auth for contract creation and management endpoints. JWT token from LCB identity server.
- Client Credentials:For document download endpoints. Uses client ID + secret. Company ID validated.
- Webhook Auth (Outbound):LCB authenticates to your webhook URL using Salesforce OAuth, Basic Auth, or OIDC — configured per integration client.
Who Benefits Most?
- Banks with Loan Origination Systems:LOS creates loan agreement in LCB via API. Customer signs via Aadhaar. Webhook notifies LOS when done. LOS downloads signed contract.
- NBFCs with Digital Lending Platforms:High-volume loan processing with automated contract creation, eStamping, and webhook-driven status updates.
- Insurance Companies:Policy management systems create insurance documents via API. Agent and customer sign remotely. Completed policy auto-syncs back.
- Any CRM or ERP:Salesforce, custom CRM, or ERP — if your system can make HTTP calls and receive webhooks, it can integrate with LCB.
FAQs
- Do I Need to Build a UI for Signing?:No. LCB handles the entire signer experience — Aadhaar gateway, eSigner, DocuSign. Your system just calls the API and receives webhooks.
- Can I Configure Which Events Trigger Webhooks?:Yes. Each integration client can configure which document statuses trigger webhook notifications.
- What Format Are Documents Sent In?:PDF only. Documents are sent as Base64-encoded strings in the API request.
- Is the API Rate Limited?:Contact/inquiry endpoints are rate limited (2 requests per 5 minutes). Core integration endpoints are not rate limited.
- Can I Test the Integration in a Sandbox?:Yes. Contact our team for sandbox credentials and a staging environment.
Your system stays in control. LCB handles the hard part — eStamping across 28+ states, Aadhaar authentication, approval workflows, and compliance. You just make API calls and receive webhooks.
Book a demo to see the integration in action, or request sandbox access to start building today.