Connect signatures to what you already use.
A single REST API plugs your ERP, your CRM or your in-house system into the pieces of the ecosystem. You take the ones you are missing; the ones you already have, you leave alone.
- SAP S/4HANA
- Oracle
- Salesforce
- Microsoft Dynamics
- Workday
- In-house system
- Webhooks
- OData
- Postman
- Multi-holding
Draw your integration in two clicks
Pick where your operation lives and which piece you are missing. The diagram and the API call build themselves: that is, literally, everything you have to connect.
Five pieces you can take separately
You don't have to adopt the whole suite to start. Each piece exposes its own API surface and connects on its own; the rest are added later without redoing the integration.
Legale Sign
Simple and advanced electronic signature inside your processes: six signature models, identity validation and legal evidence with a QR code on every document.
Legale CLM
The contract lifecycle: drafting, negotiation, signing, expirations and renewals, with the case file building itself as the process moves forward.
Legaliza
The API that connects you with notaries within the workflow: notarial authentication, notary routing by geolocation and archiving of documents validated under Law 19,799.
Legale GRC
Governance, risk and compliance on the same data: retention policies, access control and the traceability an audit or a due diligence asks for.
Digitization
The paper that still exists joins the same circuit: bulk upload, indexing and an electronic case file, so the operation is complete and not half done.
One single integration
The pieces share authentication, format and case file. Adding the next one does not open a new project: it is one more parameter in the same JSON you already have running.
An API your team understands in an afternoon
REST, JSON and two ways to authenticate. A sandbox to test with no legal effect and a Postman collection so you don't have to write the first call by hand.
Two paths, the same result
A JWT token for user sessions, or an API key for server-to-server integrations, generated from the console with an admin role.
Authorization: Bearer {{token}}
Legale-Api-Key: {{api_key}}
Accept-Language: es | en | pt
Test before it is real
https://api.legale.io/api/v2Real traffic and signatures with legal validity.https://dev.api.legale.io/api/v2No legal effect. To integrate at your own pace.Weeks, not quarters
The API key is generated, the Postman collection is imported and the first workflow runs against the test environment.
A real process —a purchase order, an addendum— travels from your system to signature and comes back with its evidence.
Document templates, signature models per use case and permissions per role are configured.
The base URL is switched, the return webhooks are enabled and the process goes live with legal validity.
SAP is where it shows most
It is the most demanding integration we do, which is why we tell it: if the circuit closes inside SAP without touching the core, it closes in any system with REST.
A purchase order, an invoice, a contract or a delivery record, with the data already in the ERP.
It builds the case file, applies the right signature model and records the legal evidence.
The status updates itself and the signed document is archived, with no emails and no downloads in between.
Formalization happens outside SAP. The ERP stays standard and upgradable, with no intrusive ABAP.
Signing happens inside SAP Fiori, in the usual flow and with one click. Minimal learning curve.
Integration through REST and OData APIs, compatible with S/4HANA and hybrid environments.
Multi-client, multi-holding and multi-SAP on the same integration, with configurable PDF templates.
One integration, every document:
Legal certainty, not just uptime
An integration is worth it if what it produces survives an audit. HTTPS-only communication, timestamped evidence and built-in retention, expiration and secure deletion policies.
Plus specific backing from Chile's Labor Directorate for employment processes:
Questions from technical teams
Do we have to use the whole ecosystem?
No. Each piece works on its own. You can connect only electronic signature, only the notary connection or only governance, and add the rest later on the same integration.
Does it work if we don't use SAP?
Yes. SAP is the case we document most because it is the most demanding, but the API is standard REST: it connects the same way with Oracle, Salesforce, Dynamics, Workday or an in-house system.
How is the integration authenticated?
With a JWT token in the Authorizationheader, or with an API key in the Legale-Api-Key header for server-to-server integrations. The key is generated from the console with an admin account.
Is there a test environment?
Yes, a sandbox with its own base URL and no legal effect, meant for integrating at your own pace. Data in that environment can be deleted without notice, so it is not used for real operations.
Does changing the signature type mean rewriting code?
No. The workflow is defined in a single JSON file and the signature technology —token, cloud certificate, self-generated signature or SMS— is changed with one parameter.
And if we need something the API does not have?
There is the Custom API, designed around specific requirements. That is where things like Bulk AES and custom registry reports live, built for operations that did not fit the standard.
Tell us which piece you are missing
Tell us which system you use and where your document process breaks. We show you the exact call that closes it, on the sandbox, in the same meeting.