Integration development
Publishing documents to identities¶
Documents can be published by client for document owner as well as for other identities.
- The user uploads the blob (click here).
- The user publishes the document with reference to the blob (click here).
- The user will create a folder (click here)- for the case when the document has no reference to the blob.
- To create the document in the root, no folder id is indicated.
- To create a document in a folder, the folder id will be indicated as the parent folder.
- The system can publish more documents into a folder, indicating the folder id as destination.
Obtaining credentials¶
MDocs accepts client certificates generated by Certification Authority of the Center of Special Telecommunications (https://pki.cts.md), by requesting a certificate for authentication for systems.
Client registration and network access¶
MDocs authenticates the clients by client certificate fingerprint. MDocs service clients must be registered in MDocs before being able to call the API.
MDocs API is accessible only to a registered set of IP addresses and, for security sensitive information systems, this means configuring routes and/or a VPN between the client and MDocs.
To register a client and get network access, please write a request by e-mail to the Service owner, providing your public IP address or the VPN assigned private IP address and the certificate fingerprint in your request.
Obtaining technical contract¶
The API documentation can be obtained from the following URL (base addresses are listed in System environments):
https://mdocs.dev.egov.md:8443/api/swagger/index.html
System environments¶
There are 2 services environments available: a testing and a production environment.
| Environment | Mdocs service URL |
|---|---|
| Staging | https://mdocs.staging.egov.md https://mdocs.dev.egov.md:8443/api |
| Production | https://mdocs.gov.md/ |