Dinero API documentation

These pages describe how to get started with the Dinero API.

Getting started

The Dinero API is REST based, which is easy to work with and familiar to developers.

The base endpoint for the current version of the API is:


To use the API, you need to apply as a developer. We will send you a Client ID and a client secret, which you should use to authenticate yourself through the API.

If you want to use an API key on behalf of your account, you will also need to obtain the key for the organization. Please navigate to the API page in Dinero to generate the key. You need an active Dinero Pro subscription for the organization that you need to access. You can upgrade your subscription on the subscription page


ClientId and ClientSecret

You will receive your API credentials on email, when you have been approved as an API partner. If you have not yet applied you can do it here

Encoded ClientId and ClientSecret

Is your encoded ClientId and ClientSecret. To get the [encodedSecret] you need to base64 encoded your ClientSecret and ClientId seperated by ':', as shown here: [client_id]:[client_secret] .

API key

The API key of the organization you want to access in Dinero. This will have be provided by your customer/user of you integration. To genereate an API key, you need to be a Dinero-Pro user, as an API partner we can grant you Pro access on your test organization, just contact our support. For a guide how to create an API key, se here


"Organization" is the term we use for the users "Firma" in Dinero. If you need a test organization, here is a guide to how you can create one.

Organization id

The organization id of the organization you want to access in Dinero. This will have to be provided by your customer/user of you integration. Here is a guide to where you can find the organization id on a Dinero organization

Ledger items

Equal to the danish "kassekladde linje".

Basic authentication

Authentication is done through the following endpoint:


Dinero uses token based authentication through OAuth2. This means that you use a token on every request to authorize yourself. Your EncodedClientIdAndSecret and the target organizations API-key is used with the above endpoint, in exchange for a token, which you then append on every future requests.
You'll need a new token for each organization you want to access.

POST https://authz.dinero.dk/dineroapi/oauth/token
Authorization: Basic [EncodedClientIdAndSecret]
Content-Type: application/x-www-form-urlencoded
grant_type=password&scope=read write&username=[API-key]&password=[API-key]

If your request was composed correctly, and your credentials were correct, the server will return an access_token in JSON format for you to use:


Basic usage

After obtaining an access token, you append it on every request using the following header:

Authorization: Bearer [access_token]

Where [access_token] should be replaced with the token you just received.

Here is an example of how to create four new ledger items on the current ledger

POST https://api.dinero.dk/v1/[organization_id]/ledgeritems HTTP/1.1
Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9(...)
Host: api.dinero.dk
Content-Type: application/json
Content-Length: 821
    {"VoucherNumber":3,"AccountNumber":1000,"AccountVatCode":"I25","Amount":-500,"BalancingAccountNumber":null,"BalancingAccountVatCode":null,"Description":"produkt, lille","VoucherDate":"2015-05-27"},
    {"VoucherNumber":3,"AccountNumber":1300,"AccountVatCode":"none","Amount":-25,"BalancingAccountNumber":null,"BalancingAccountVatCode":null,"Description":"Momsfrit fragt","VoucherDate":"2015-05-27"},
    {"VoucherNumber":3,"AccountNumber":53000,"AccountVatCode":null,"Amount":525,"BalancingAccountNumber":null,"BalancingAccountVatCode":null,"Description":"Faktura 12","VoucherDate":"2015-05-27"},
    {"VoucherNumber":4,"AccountNumber":2000,"AccountVatCode":"none","Amount":100,"BalancingAccountNumber":52000,"BalancingAccountVatCode":null,"Description":"Vareforbrug ifbm fak 12","VoucherDate":"2015-05-27"},
See the API endpoints documentation for a description of all available endpoints

Post Image

An example of how a post call to our files service could look like:
POST https://api.dinero.dk/v1/[organization_id]/files/?fileName=sample-invoice.jpg HTTP/1.1
Authorization: Bearer eyJ0eXAiOiJKV1QiLC....
Accept: application/json
Content-Type: multipart/form-data; boundary="-------abcdefg1234"
Host: api.dinero.dk
Content-Length: 313036
Expect: 100-continue
Connection: Keep-Alive

Content-Type: image/jpeg
Content-Disposition: form-data; name=image; filename=sample-invoice.jpg; filename*=utf-8''sample-invoice.jpg


Filters are not available on all properties, so be sure to check the endpoints queryFilter URI parameter description to see which. If the endpoint do not contain a queryFilter URI parameter, then it does not support filtering.

Each filter command is built after the structure: [PropertyName] [Operator] '[Value]'

Be aware that the [Value] is not case sensitive. And remember the ' around it.

Each filter command should be separated with: ;

Name Types Operator Example
Equals string, int, bool eq Name eq ’John Doe’
Contains string contains Name contains ’John D’




Get methods that potentially has a very large output implements pagination. It can maximum return 1000 entries per page, if a higher pageSize is given an Exception with error code 43 is thrown. The pagination defaults to a pageSize of 100 entries, and returns the first page if left empty.

The pagination URI properties are listed below:

Name Description Type Additional information
page The 0-based page number integer Default value is 0
pageSize The maximum number of items to include in a page. Max 1000. integer Default value is 100. Max value is 1000.


There are no limit on the number of API requests per day. However, requests will be rate-limited if too many calls are made within a short period of time. Rate limiting is considered on a per API-key basis. An organization can have multiple API-keys associated to it. Each api-key will be considered separately. There are currently no limitations on the client_id

If you hit the rate limit, this is the body of the HTTP 429 message that you will see:

API calls quota exceeded! (...)

If Dinero detects that the API resources are being exhausted by a single client integration and it is evaluated by Dinero to hurt the general service of the API to other customers, Dinero can decide to revoke the access for single clients. Dinero will always strive to solve such issues in dialog with the integrating partner before any counter measures are taken.