API e-Cont.md reference

API reference
Changed: 08.10.2023 19:16


This is the e-Cont.md API documentation for issuing and circulation of electronic invoices for payment.

Our API has been designed to meet all the billing needs of your business or web application and make the integration process as easy as possible. Through the API, we can help you seamlessly manage billing, payments, subscription billing, pricing, and more.

We have developed the e-Cont.md API in accordance with the use of elements of REST technology (wiki).

Here are a few pages that you might find helpful in addition to this API reference.

API Endpoint

All API calls must be made to the API endpoint: https://api.diginet.md.

All responses will be in the open standard JSON data interchange format. The input passed through the request body can be encoded with JSON. If you are using a JSON body, specify the Content-Type header as application/json. Use UTF-8 encoding for full compatibility with different languages.

In the API, dates are represented in the format "YYYY-MM-DD hh:mm:ss", for example: 2018-02-21 12:10:25 Each object, such as a customer or an account, has a unique integer identifier (integer).


Some methods support returning a PDF response instead of JSON if you set the Accept header to application/pdf.

For example, the get invoice method might return a PDF file. Endpoints that support PDFs are noted in the documentation.

Getting help or getting involved

We have made this document public. Please report any problems or suggestions in the e-Cont.md API documentation. Any requests for changes to this document are also welcome! If you need help using the API or need to discuss something sensitive, please email us at support@e-cont.md.


API for user authentication uses the technology of unique keys (tokens). Valid API keys are required for all requests.

Getting an API Key

The API key can be obtained by logging into the e-Cont.md system and then selecting SETTINGS → “{{ YOUR OFFICE }}” → “Online Invoicing” → “E-Invoice issuing”.

Select the "Universal Data Exchange - API" section and copy the two keys:

  • Client ID is a unique key for your account
  • Token is the unique key of your unit

Use these keys in your queries