Connect your ERP and CRM
to Eosten DMS.
Your CRM, ERP, HRMS or core-banking system files its documents straight into Eosten DMS. Give it its own key, limited to the folder it writes to. It sends each document with its metadata, fetches it again when it needs to, and your people find everything inside the DMS.
Four steps, one key.
A REST API with JSON answers. No connector to install and no middleware to run.
Create a key for the folder
An admin creates a scoped API key bound to the section or folder your system writes to. It's shown once, stored only as a hash, and works only inside that folder tree.
Push documents with metadata
Your system uploads each document with its metadata in the same request. Required fields are checked, and an incomplete upload is refused as a whole, so nothing lands half-filed.
Pull and download
Read a document's details and metadata, list the folder (filtered by name or document number), and download the file whenever your system needs it.
People search in the DMS
Everything your system files is numbered, indexed and searchable by the people allowed to see it, with the folder's permissions, workflows and retention already in place.
The same path as a person's upload
A document that arrives through the API goes through exactly the same finishing step as one dragged into the browser. Nothing is skipped because a machine sent it.
- Checked: the folder's permissions, the file's real type (executables and macro documents are refused) and the storage quota.
- Filed: metadata saved in the same transaction, the document number issued from the folder's scheme, and the folder's retention policy applied.
- Put to work: OCR and indexing, workflows that start on a new file, watchers notified, and Aadhaar masking where the optional module is on.
- Recorded: an entry in the audit trail, under the key's own service account.
Three things cover
most integrations.
When you start an integration, we share the API reference and working examples with your developers, and help with the first connection.
File a document with its details
One request carries the file and its metadata, using the fields of the folder's metadata template. The answer includes the new document's number if the folder issues them. If a required field is missing, nothing is stored and your system is told why.
Read it back and download it
With the same key, your system can read a document's details, download the file, or list its folder filtered by document number or name. Personal-data fields come back masked to a scoped key.
Find documents by metadata
Search combines conditions, sorts by any field and pages through results, always following the caller's permissions. It needs a person's session or a personal key, so an integration's scoped key stays inside its own folder.
Each scoped key comes with its own integration guide inside Eosten DMS, showing its folder and what it can do. Ask for the API reference
What each system
usually files, and where.
Common ways to integrate a document management system with ERP, CRM and line-of-business systems. Your folders and fields will follow your own process.
ERP: invoices and purchase orders
Each posted invoice or PO is filed as it's created.
- Folder
- Finance / Invoices / FY 2026-27
- Metadata
- Invoice number, vendor, vendor GSTIN, amount, invoice date
- Then
- The folder's scheme numbers each invoice, and a workflow can send large amounts for approval.
CRM: KYC and contracts
KYC documents and signed contracts land in the customer's own folder.
- Folder
- Customers / <customer ID>
- Metadata
- Customer ID, PAN, document type (KYC, contract, mandate)
- Then
- With the optional masking module on this folder, Aadhaar cards are masked as they arrive.
HRMS: employee documents
Offer letters, ID proofs and appraisals, filed per employee.
- Folder
- HR / Employees / <employee ID>
- Metadata
- Employee ID, document type, joining date
- Then
- Only HR has access, and the folder's retention policy decides how long records are kept.
Core banking or LOS: loan files
The loan origination system archives each file at sanction.
- Folder
- Loans / <branch> / <loan account>
- Metadata
- Loan account number, customer ID, sanction date, amount
- Then
- Required fields stop an incomplete file, and a legal hold freezes a disputed one.
Scanning station: inward scans
Your scanning software saves each batch as PDF; a small script sends it in.
- Folder
- Scans / Inward / <branch>
- Metadata
- Batch number, branch, scan date
- Then
- OCR makes every page searchable. Eosten DMS doesn't drive the scanner itself.
Your system?
Tell us what it should file and where. We'll help you map folders, metadata fields and keys before you write a line of code.
Exactly what a key can do,
and what it can't.
A scoped key is a narrow, purpose-built door. That's what makes it safe to hand to another system.
A scoped key can
- List and browse its own folder tree
- Upload one file per request, with metadata, a comment and tags
- Read a document's details and metadata (personal-data fields come back masked)
- Download files
- Delete files, which go to the recycle bin
- Create sub-folders, unless the key is for a single folder
By design, it can't
- Search across the workspace. Use a personal key, or let people search in the app
- Change a document's metadata after upload
- Add new versions of a document
- Change settings, permissions, users or workflows
- Reach anything outside its folder
Shown once, stored as a hash
The full key appears only when it's created or rotated. Eosten DMS keeps a hash of the secret, never the secret itself.
Revocable at any time
Rotate a key to issue a new secret. Revoking it disables its service account and removes its folder access at once.
Never in a web address
The key travels with each request, never in a URL. It works only while the key, its service account and the workspace are active.
The same rules as people
Every call follows the folder's permissions and the workspace's IP allow-list, and is recorded in the audit trail under the key's service account.
Field keys matter
Use the metadata field keys your admin gives you. A key the folder doesn't recognise is ignored rather than saved; a missing required field refuses the whole upload.
Made for everyday filing
Rate limits apply per client address (by default 600 requests and 60 uploads a minute). For a large back-file, ZIP import or a planned migration is usually the better route; we'll help.
More on how keys fit the wider security model on the security page, and the full list of API capabilities under features.
Masked on arrival,
whoever sends it.
With the optional Aadhaar masking module, choose the folders where masking runs automatically. Every document your systems push into one of them, or into a folder below it, is masked shortly after it's stored: the Aadhaar number and the QR code, exactly as for a person's upload.
Good to know
- Masking is an optional module of Eosten DMS, and the same engine is sold on its own as Eosten Aadhaar Masking.
- The masked file replaces the original; no unmasked copy is kept.
- Documents it can't touch (on legal hold, locked or signed) are listed in a report for review.
- Masking is automated, so review the results for critical documents.
Planning an
integration?
Tell us the system and what it should file. We'll help you map folders, metadata and keys, and test the first calls with you.