Contacts
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.
The primary key of a company to filter on.
A comma separated list of company primary keys.
12345,9876Get successful
1Get successful
Add a contact to a specific company in the requester's address book.
The company can be identified either by its pk or its remote_id.
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/"
687cddac-dbd2-11ea-9024-0242ac130006Date of creation on our server
2020-12-22T15:31:39.26167ZThe id of the contact in your system
CONTACT_123Create 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 uid then
-
replace the
uidvalue 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)
Empty body
Empty body
No content
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 uid then
-
replace the
uidvalue 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
687cddac-dbd2-11ea-9024-0242ac130006Date of creation on our server
2020-12-22T15:31:39.26167ZAdèleBouvet[email protected]+33600000000The id of the contact in your system
CONTACT_123Ignore. Dashdoc technical data.
Ignore. Dashdoc technical data.
Ignore. Dashdoc technical data.
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 uid then
-
replace the
uidvalue 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)
Update successful
687cddac-dbd2-11ea-9024-0242ac130006Date of creation on our server
2020-12-22T15:31:39.26167ZAdèleBouvet[email protected]+33600000000The id of the contact in your system
CONTACT_123Ignore. Dashdoc technical data.
Ignore. Dashdoc technical data.
Ignore. Dashdoc technical data.
Update successful
Last updated
Was this helpful?