Companies
Authentication is token based. You can issue a token for your API request from the 'API' section of the settings menu. The token MUST be sent in a Authorization header with each request.
Example of authenticated request
$ curl -X GET -H "Authorization: Token <your token>" "https://api.dashdoc.eu/api/v4/"
A page number within the paginated result set.
Case insentive filter on company name
Filter companies updated after or at a certain date
Filter companies updated before or at a certain date
Filter companies updated after a certain date
Filter companies updated before a certain date
Get successful
Get successful
Creates a company in your address book.
Controls occur to prevent from creating distinct companies objects that would actually represent the same.
Unicity control is performed on attributes in this order to determine if it already exists:
-
remote_id -
trade_number -
name
Authentication is token based. You can issue a token for your API request from the 'API' section of the settings menu. The token MUST be sent in a Authorization header with each request.
Example of authenticated request
$ curl -X GET -H "Authorization: Token <your token>" "https://api.dashdoc.eu/api/v4/"
Transport Bouvet[email protected]Only the 2-character codification is accepted (ISO 3166-1 alpha-2)
FRThe ID of the company in your system. It has to be unique among all your companies.
The id of the company in your invoicing system.
COMP_456Notes for this company, only visibile to your team members
Create successful
Create successful
Authentication is token based. You can issue a token for your API request from the 'API' section of the settings menu. The token MUST be sent in a Authorization header with each request.
Example of authenticated request
$ curl -X GET -H "Authorization: Token <your token>" "https://api.dashdoc.eu/api/v4/"
If you choose to identify an object with its remote_id instead of its pk then
-
replace the
pkvalue with theremote_idvalue in the URL -
specify
lookup_field=remote_idin the query parameters
Used to specify what field is used in the URL to identify the object you're requesting, e.g. with the remote_id (see path parameters)
Get successful
Get successful
Authentication is token based. You can issue a token for your API request from the 'API' section of the settings menu. The token MUST be sent in a Authorization header with each request.
Example of authenticated request
$ curl -X GET -H "Authorization: Token <your token>" "https://api.dashdoc.eu/api/v4/"
If you choose to identify an object with its remote_id instead of its pk then
-
replace the
pkvalue with theremote_idvalue in the URL -
specify
lookup_field=remote_idin the query parameters
Used to specify what field is used in the URL to identify the object you're requesting, e.g. with the remote_id (see path parameters)
Only updatable by the creator of the company, and if the company hasn't subscribed to Dashdoc
Transport BouvetOnly updatable by the creator of the company, and if the company hasn't subscribed to Dashdoc
Only updatable by the creator of the company, and if the company hasn't subscribed to Dashdoc
[email protected]Only updatable by the creator of the company, and if the company hasn't subscribed to Dashdoc
Only updatable by the creator of the company, and if the company hasn't subscribed to Dashdoc
Only updatable by the creator of the company, and if the company hasn't subscribed to Dashdoc
Only the 2-character codification is accepted (ISO 3166-1 alpha-2)
FRThe ID of the company in your system. It has to be unique among all your companies.
The id of the company in your invoicing system.
COMP_456Notes for this company, only visibile to your team members
Update successful
Update successful
Last updated
Was this helpful?