forked from teamleadercrm/api
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathapiary.apib
4378 lines (3495 loc) · 163 KB
/
apiary.apib
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
FORMAT: 1A
HOST: https://api.teamleader.eu
# Teamleader API
This is the new Teamleader API. We will make additions and changes to this API, but don't worry; we will keep the documented endpoints backwards compatible for the lifetime of this major API version.
Do you have any feedback, do you miss functionality to support your use case? Let us know via [api@teamleader.eu](mailto:api@teamleader.eu).
## AP-What?
An API is an Application Programming Interface. It is used to programmatically interact with Teamleader, integrate with other software tools or add custom functionalities to Teamleader.
Before creating a new integration, make sure to check our existing integrations built by our community in our [Teamleader Marketplace](https://marketplace.teamleader.eu).
## General principles
### Endpoints
Our API consists of HTTP RPC-style methods, in the form of `https://api.teamleader.eu/resource.action`.
We chose this action based approach over the more popular REST, because it enables us to have domain related actions on resources such as `invoices.book`, `timetracking.start` and `timetracking.stop`.
### Requests
All methods must be called using HTTPS. Data is passed as JSON data in a POST request or as GET query parameters.
For more complex actions we recommend using POST requests with JSON:
```
POST https://api.teamleader.eu/invoices.list
{
"filter": {
"department_id": "9d4096c3-813f-4bd5-b3c4-4091807b5b74"
},
"page": {
"size": 50,
"number": 3
}
}
```
The GET equivalent:
```
GET https://api.teamleader.eu/invoices.list?filter[department_id]=9d4096c3-813f-4bd5-b3c4-4091807b5b74&page[number]=3&page[size]=50&company_id=3250c613-c478-4a43-9640-b97da923eb21
```
### Responses
Both single objects and collections are returned as JSON objects, keyed by `data` in the top level of a JSON object:
```json
{
"data": {
"id": "f1dfb84c-3c29-4548-9b9b-9090a080742a",
"first_name": "Erlich",
"last_name": "Bachman",
"salutation": "Mr",
"email": "info@piedpiper.eu"
}
}
```
Responses may also contain meta data for pagination.
Sample response with pagination:
```json
{
"data": [
{
"id": "f1dfb84c-3c29-4548-9b9b-9090a080742a",
"first_name": "Erlich",
"last_name": "Bachman",
"salutation": "Mr",
"email": "info@piedpiper.eu"
},
{
"id": "f1dfb84c-3c29-4548-9b9b-9090a080742b",
"first_name": "John",
"last_name": "Doe",
"salutation": "Mr",
"email": "john@piedpiper.eu"
}
],
"meta": {
"page": {
"size": 20,
"number": 2
},
"matches": 200
}
}
```
### Errors
Errors are always returned as an array of error objects, keyed by `errors` in the top level of a JSON object:
```json
{
"errors": [
{
"title": "Company name must not be empty"
}
]
}
```
### Rate limiting
To ensure a fast and predictable experience for everyone, all our API endpoints have a rate limit of **100 calls per minute** for each integration (or client id) to a Teamleader account.
When you go over this limit, our API will respond with a `HTTP 429 Too Many Requests error`.
If your integrations need a higher limit, send us an email at [api@teamleader.eu](mailto:api@teamleader.eu) with a detailed explanation of why you need an increased rate limit.
### Status codes
When objects are created, we return a `201` response containing the `id` and `type` of the new resource:
```json
{
"type": "contact",
"id": "9d4096c3-813f-4bd5-b3c4-4091807b5b74"
}
```
When objects are updated or actions are performed, we often return an empty response with a `204` status code.
Common used status codes:
- `200` - OK
- `201` - Created, when resources are created
- `204` - No Content, on resource updates or actions
- `400` - Bad Request, the request contains invalid data or references non-existing resources
- `401` - Unauthorized, invalid or missing access token
- `403` - Forbidden, not allowed to access this resource
- `404` - Not Found, resource not found
- `429` - Too Many Requests, your client has reached the API rate limit
- `500` - Internal Server Error, something went wrong on our end
## Authentication
### OAuth 2
OAuth 2 is an authorization framework that allows a user to grant limited access to data in a Teamleader account, without having to expose their credentials.
To get access to the protected resources using our API, OAuth 2 uses access tokens. An access token is a string representing the granted permissions. Access tokens can be obtained after a user has completed the OAuth 2 authorization flow.
Before starting, you will need to register your integration (an OAuth 2 client) on our [Marketplace](https://marketplace.teamleader.eu/build). Each registered integration is assigned a unique `client_id` and `client_secret`, which is used in the OAuth 2 authorization flow. Note that the `client_secret` key should not be shared or embedded in client-side code.
When you register an integration on our [Marketplace](https://marketplace.teamleader.eu), it is required to select all *scopes* your integration wants access to.
For more detailed information about OAuth 2, we recommend reading [this article](https://auth0.com/docs/protocols/oauth2).
### Authorization flow
To get access to a user's Teamleader data using the *authorization code grant type*, redirect users to the Teamleader authorization page:
`https://app.teamleader.eu/oauth2/authorize`
The required GET parameters are:
- `client_id` - issued when you create your integration
- `response_type` - must be "code"
- `state` - unique string to be passed back upon completion (optional)
- `redirect_uri` - URL to redirect back to after authorization
> A list of allowed redirect URIs needs to be configured on your integration's [settings page](https://marketplace.teamleader.eu/build). Only redirect URIs matching one of these whitelisted URIs will be accepted. This is a security measure to prevent malicious users to impersonate your integration.
After logging in, the user will be asked to authorize your integration to access the data in their account. You will only be granted access to certain Teamleader data, based on the scopes you have selected on your integration's [settings page](https://marketplace.teamleader.eu/build).
If the user authorizes your integration, they will be redirected to the specified `redirect_uri` with a temporary authorization code and the original `state` parameter. If the `state` parameter does not match the original value, the response may have been created by a third party and should be ignored.
`https://YOUR_REDIRECT_URI?code=CODE&state=STATE`
If the user denies your integration, he will be redirected to the `redirect_uri`, with an `error` parameter:
`https://YOUR_REDIRECT_URI?error=access_denied`
### Obtaining access tokens
After receiving the authorization code from the previous step, an access token can be requested to make API calls. Note that authorization codes can only be exchanged for an access token once and expire 10 minutes after issuance. To exchange the code for an access token, send an HTTP POST request to the following endpoint:
`https://app.teamleader.eu/oauth2/access_token`
The required POST parameters are:
- `client_id` - issued when you register your integration
- `client_secret` - issued when you register your integration
- `code` - the authorization code
- `grant_type` - must be "authorization_code"
- `redirect_uri` - the original submitted redirect URL
It is recommended to add `content-type` header to this request. Supported content types are:
- application/x-www-form-urlencoded
- application/json
You will receive a JSON response containing an `access_token` and `refresh_token`:
```
{
"token_type": "Bearer",
"expires_in": 3600,
"access_token": "ACCESS_TOKEN",
"refresh_token": "REFRESH_TOKEN"
}
```
These access tokens are also known as bearer tokens. You can use this token to call API endpoints on behalf of the user, by adding it to the API request as an `Authorization` header.
```
GET https://api.teamleader.eu/contacts.list HTTP/1.1
Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciO...
Accept: application/json
```
Access tokens expire shortly (usually 1 hour) after they are issued for security reasons. If your integration needs to communicate with our API beyond the access token's lifespan, you will need to request a new access token using the refresh token which was issued with the access token. Note that refresh tokens can only be used once to get a new access token and refresh token.
### Using refresh tokens
If an access token is expired, a new access token and refresh token pair can be obtained by sending an HTTP POST request to the following endpoint:
`https://app.teamleader.eu/oauth2/access_token`
The required POST parameters are:
- `client_id` - issued when you register your integration
- `client_secret` - issued when you register your integration
- `refresh_token` - the refresh token
- `grant_type` - must be "refresh_token"
Refresh tokens will continue functioning until the user revokes them or uninstalls your integration.
### Client-side authorization (implicit grant)
Your client secret must remain private and can not be embedded within client side applications such as browser plugins. For these types of applications, we have an alternative authorization method called using the [implicit grant](https://tools.ietf.org/html/rfc6749#section-1.3.2).
The implicit grant is a simplified authorization code flow optimized for clients implemented in a browser using a scripting language such as JavaScript. In the implicit flow, instead of issuing the client an authorization code, the client is issued an access token directly.
Similar to the regular flow, users are redirected to the Teamleader authorization page, but use `token` as the `response_type`:
`https://app.teamleader.eu/oauth2/authorize`
The required GET parameters are:
- `client_id` - issued when you create your integration
- `response_type` - must be "token" (instead of "code")
- `state` - unique string to be passed back upon completion (optional)
- `redirect_uri` - URL to redirect back to after authorization
> A list of allowed redirect URIs needs to be configured on your integration's [settings page](https://marketplace.teamleader.eu/build). Only redirect URIs matching one of these whitelisted URIs will be accepted. This is a security measure to prevent malicious users to impersonate your integration.
After authorization, the user is redirected to the `redirect_uri` with the following parameters in the **fragment part of the url**:
- `token_type` - with the value "Bearer"
- `expires_in` - the TTL for this access token in seconds
- `access_token` - the access token
- `state` - the state parameter sent in the original request
Example:
`https://YOUR_REDIRECT_URI#token_type=Bearer&expires_in=900&access_token=TOKEN&state=STATE`
Note that the implicit grant does not return refresh tokens and that our access tokens have a short TTL value. If you opt for this authorization method, you will have to go through the authorization flow every time you want to make API calls on behalf of the user. Keep this in mind while developing client-side applications.
### User Identity
To retrieve information about the user who authorized your application (the resource owner), call the `users.me` API endpoint:
`https://api.teamleader.eu/users.me`
### PHP code example
You can find a (very) minimal PHP code example, showing how to start the OAuth 2 authentication flow and retrieve the user's identity using the obtained access token.
[https://github.com/teamleadercrm/api/blob/master/examples/oauth2.php](https://github.com/teamleadercrm/api/blob/master/examples/oauth2.php)
A Teamleader PHP SDK is under development. In the meanwhile, we recommend using packages such [Guzzle](http://docs.guzzlephp.org/en/stable) or the [League OAuth2 client](http://oauth2-client.thephpleague.com).
<a name="sideloading"></a>
## Sideloading
Sideloading (or compound documents) allows you to retrieve relevant related items as part of a single request. For example, a deal has a reference to a lead which can either be a contact or a company:
```
{
"data": {
"id": "f6871b06-6513-4750-b5e6-ff3503b5a029",
"title": "Deal with ACME",
"lead": {
"customer": {
"type": "company",
"id": "2659dc4d-444b-4ced-b51c-b87591f604d7"
}
}
}
}
```
Relationships are always represented by an object with a type/id combination. All of these relationships are candidates for sideloading.
To sideload relationships, use the dot-notation reference of the relationship's property and add it as an `include` parameter to your JSON body or your URL. In this case of our deal's customer, that would be `include=lead.customer`.
The sideloaded relationships are returned as part of an `included` property in the response body.
```
{
"data": {
"id": "f6871b06-6513-4750-b5e6-ff3503b5a029",
"title": "Deal with ACME",
"lead": {
"customer": {
"type": "company",
"id": "2659dc4d-444b-4ced-b51c-b87591f604d7"
}
}
},
"included": {
"company": [
{
"id": "2659dc4d-444b-4ced-b51c-b87591f604d7",
"name": "ACME"
}
]
}
}
```
Note that the sideloaded relationships are indexed based on their object type. Use the `type` property from your original relationship object to search for the sideloaded relationship in the `included` section.
Multiple relationships can be sideloaded at the same time by passing them as a comma-separated value such as `include=lead.customer,responsible_user`.
Sideloading is supported on every endpoint which returns objects.
## Changes & upgrades
We want to keep this API backwards compatible as long as possible, but at the same time, we need to make changes to it to match our evolving product.
Therefore we assigned a dated version to your API client when it was created.
This version controls the API and webhooks behaviour for your API client.
When we change the API in a backwards-incompatible way, we release a new dated version.
To avoid breaking your code, you stay on your assigned version until you [upgrade your API version](#upgrading-your-api-version).
### Types of changes
We consider the following changes to be backwards-compatible:
- Adding new API endpoints.
- Adding new optional parameters to existing API requests.
- Adding new properties to existing API responses.
- Adding new webhook types.
- Making existing parameters optional.
- Changing the order of properties in existing API responses.
- Fixing (potential) bugs that made an endpoint unusable (HTTP 500 errors).
- (Currently, we also hold ourselves the right to return a different error format, as there is still room for improvement)
We consider the following changes to be backwards-incompatible:
- Renaming or removing an endpoint.
- Renaming or removing a parameter of API requests.
- Renaming or removing a property of API responses.
- Changing the format of a parameter of API responses (eg. integer to float)
- Making validation of a parameter more strict (eg. making it required)
- Returning a different HTTP status code.
<a name="additions"></a>
### Additions
We list all backwards-compatible additions here. These are currently available in all published versions.
(There is also a [list of backwards-incompatible upgrades](#changelog) available, but those only apply if you [upgrade your API version](#upgrading-your-api-version).)
#### Latest
- We added actuals and budget to `projects.list`, `projects.info`, `milestones.list`, and `milestones.info`.
- We added the `description` field to `milestones.info`, `milestones.create`, and `milestones.update`.
- We added an `ids` filter to `lostReasons.list`.
- We added `lost_reason` to the response of `deals.info`.
- We added `lost_reason` to the response of `deals.list`. This is composed of a `lostReason` object along with a more elaborate `remark`.
- We added format `ubl/e-fff` to `invoices.download`.
- We added filters `estimated_closing_date_from` and `estimated_closing_date_until` to `deals.list`.
- We added a new sorting option `weighted_value` to `deals.list` and will allow ascending as well as descending orders on sorts.
The default remains created_at and descending as before if nothing is passed.
- We added the `weighted_value` to the response of both `deals.list` and `deals.info` requests.
- We added the `extra_option_allowed` information (for single select custom fields) to `customFieldDefinitions.list` and `customFieldDefinitions.info` endpoints.
- We added format `ubl/e-fff` to `creditNotes.download`.
- We added a filter `term` to `invoices.list`.
- We added the `purchase_order_number` to the response of both `deals.list` and `deals.info` request.
- We added the `summary` to the response of both the `deals.list` and `deals.info` request. The `summary` can also be added and updated through the `deals.create` / `deals.update` endpoints.
- We added `depends_on` to the `milestones.info` and `milestones.list` endpoints.
- We added `dependency_for` to the `milestones.info` and `milestones.list` endpoints. This indicates all the milestones for which the current milestone is a dependency.
- We added `depends_on` to the `milestones.create` and `milestones.update` endpoints. It allows setting a dependency on another milestone of the same project.
#### October 2019
- We added `milestones.delete`.
- We added a `estimated_closing_date` filter to `deals.list`.
- We added a filter `created_before` to `deal.list`.
- We modified filter `responsible_user_id` in `deal.list` to also accept an array of responsible_user_ids.
- Task custom fields are now included as `custom_fields` on `tasks.info`. They can also be added and updated through the `tasks.create` / `tasks.update` endpoints.
#### July 2019
- We added an `updated_since` filter to `products.list`
- We added `project` to `tasks.info` and `tasks.list`.
- We added a filter by `subject` to `timeTracking.list`.
- A `task_id` filter has been added to `/events.list`.
- We added a `term` filter to `milestone.list`.
#### June 2019
- We added a `term` filter to `tasks.list`.
- We added `tasks.complete` and `tasks.reopen` endpoints.
- We added `due_by` and `due_from` to `tasks.list` filters.
- We added a `tasks.schedule` endpoint.
- We added the ability to sort `tasks.list` based on a descending `due_at`.
- `tasks.info` and `tasks.list` now return information about the customer.
- We added `customer` parameter to `tasks.create` and `tasks.update`.
- In order to link milestones and deals to a task, we added `milestone_id` and `deal_id` as optional parameters to `tasks.create` and `tasks.update`.
- `tasks.list` and `tasks.info` now return the milestone and deal objects.
#### May 2019
- We added a `started_at` property to `timers.update` in order to be able to update the start time of a running timer.
- We added `sent` as a boolean to `invoices.info` and `invoices.list`.
- We added an optional filter on `ids` to `invoices.list`.
- We added `creditNote.booked` and `product.added` to the available webhooks list.
#### April 2019
- In `users.info`, we added the `status` property to the response since it is now possible to retrieve deactivated users.
- In `users.list`, you can now also request deactivated users, by using a new filter on `status`.
By default, the endpoint keeps returning active users only. The status is also returned in the response data.
- We've added a `products.add` endpoint.
Because you can provide the selling price of a product in this endpoint, we also return it in `products.info` from now on.
- We now also return the `payment_reference` of an invoice in the `invoices.list`.
We also made it filterable through the `payment_reference` filter.
- We added the `purchase_order_number` to all relevant endpoints (`invoices.draft`, `invoices.update`, `invoices.info` and `invoices.list`).
The property is also filterable through the `purchase_order_number` filter.
- We added `currency_exchange_rate` to `quotations.info`.
- The `events.list` endpoint now has an optional filter property `ids`.
- The `tasks.list` endpoint now has an optional filter property `ids`.
- We added an `invoices.credit` endpoint.
#### March 2019
- On `invoices.draft` and `invoices.update` you can now also provide (a) global discount(s) through the `discounts` property.
- We've published a bunch of `tasks` endpoints (`tasks.list`, `tasks.info`, `tasks.create`, `tasks.update`, `tasks.delete`).
- We now also return a `currency_exchange_rate` on all `.info` endpoints where we support multi-currency.
That is `quotations.info`, `invoices.info` and `creditNotes.info`.
#### February 2019
- We now also return the `invoicing_method` of a milestone. Both in `milestones.list` and `milestones.info`.
- We now expose the invoiceability of time trackings and running timers. You can now use the `invoiceable` property on the following endpoints:
- `timeTracking.list`
- `timeTracking.info`
- `timeTracking.add`
- `timeTracking.update`
- `timers.current`
- `timers.start`
- `timers.update`
We also return an `invoiceable` preference in the `users.me` endpoint that exposes whether a user prefers to track time by default as invoiceable or not.
- We've added a `national_identification_number` property on contacts.
You can read it from `contacts.list` and `contacts.info`.
It's also writeable through `contacts.add` and `contacts.update`.
- Invoicing custom fields included as `custom_fields`.
They are returned in `invoices.info`.
They can be added or updated through `invoices.draft` and `invoices.update`.
- Deal can now be filtered with a `term` in `deals.list`.
We will return deals of which the term is part of the title, reference or customer's name.
- We have created a way to fetch more data about related resources: sideloading.
More information can be found [here](#sideloading).
- We didn't provide you with a way to find the uuid of a quotation.
Based on a v1 deal id, you can now retrieve the uuid of a quotation with `migrate.id`.
#### January 2019
- The `projects.list` endpoint has an optional filter to filter on `term` now.
We return projects for which the term appears in the title or description.
- During `invoices.draft` and `invoices.update`, we now allow you to provide a `withholding_tax_rate_id`.
Don't worry if you don't know what this is. Withholding taxes only apply in certain countries, eg Spain or Italy.
- We added a filter on `term` in `users.list`.
We return those users who have the term in their first name, last name or email address.
- We already had a part of the products APIs for our own usage, but since it might be useful to you, we are making it public.
So `products.list` and `products.info` are now available for usage.
<a name="upgrading-your-api-version"></a>
### Upgrading your API version
This documentation only reflects the latest version of the API.
If you need to make changes to your client or you want to make use of the latest feature, you might need to upgrade your API version.
You can find your current API version, in the `X-Api-Version` header on any API response.
The current latest version is **2019-10-09**.
After checking the API [changelog](#changelog) to see which endpoints work differently, you can upgrade your API version:
Send an `X-Api-Version` header containing the identifier of a version (newer than your current version) with your requests.
_This will only affect the version for those API calls and won't affect any other calls done by your client._
<a name="changelog"></a>
### Changelog
We list all backwards-incompatible changes here. As described above, new additions and forwards-compatible changes don’t need a new API version and can be found [here](#additions).
#### 2019-10-09
- We added `billing_method` and `budget`, and `billing_method` and `price` to `milestones.create`.
- When choosing `time_and_materials` or `non_invoiceable` as the billing method, you can provide a `budget`.
- When choosing `fixed_price` as the billing method, you need to provide the `price`.
#### 2019-07-03
- The property `todo` has been renamed to `task` on the following endpoints:
- `events.list`
- `events.info`
- We renamed the `context` field for work orders on customFieldDefinitions from `werkbonnen` to `work_orders`
- The property `due_at` was removed in favour of `due_on`. Additionally, `due_on` is a date with format `YYYY-MM-DD`, instead of a ISO8601 datetime. These changes affect the following endpoints:
- `tasks.info`
- `tasks.list`
- `tasks.create`
- `tasks.update`
- We won't accept `project` as a `subject` anymore in `timeTracking.add`, `timeTracking.update`, `timers.start` and `timers.update`.
We wrongly accepted this in the past, but time tracking always needs to be coupled to a milestone. Please use the `milestone` subject instead.
For older versions, we will link the time tracked to the oldest `open` milestone. If there is no `open` milestone, it's linked to the most recent `closed` or `done` milestone.
#### 2019-03-13
- The property `tax` has been changed. Instead of giving you the `rate` of the tax it now shows the `id` and the `type` of the tax. This has been changed on the following endpoints:
- `invoices.info`
- `creditNote.info`
- `quotations.info`
- We simplified the `products.info` and `products.list` endpoints:
- `name` and `description` are no longer wrapped in a `translations` object.
- `external_id` was renamed to `code`
- `prices` are temporarily no longer returned, to avoid confusion, as they didn't take into account price lists
#### 2019-01-24
- Previously, the `invoices.info` endpoint returned an _non-existing_ or _empty_ `extended_description` as an empty string, while `invoices.draft` and `invoices.update` didn't allow an empty string as `extended_description`.
From now on, `invoices.info` will return an _non-existing_ or _empty_ `extended_description` as `null`, to make this more consistent and interchangeable.
- Invoices can now have three statuses (`draft`, `outstanding` or `matched`) instead of two (`draft` or `booked`).
Therefore the `status` property in `invoices.list` and `invoices.info` will either return `outstanding` or `matched` for invoices that were previously just `booked`.
This is also reflected in the `status` filter on `invoices.list`: to allow you to still query all `outstanding` and `matched` invoices (previously all `booked`) , it now *only* accepts an array of filter values (eg. `["outstanding", "matched"]` or `["draft"]`).
- The property `local_business_number` was renamed to `national_identification_number` on the following endpoints:
- `companies.info`
- `companies.list`
- `companies.add`
- `companies.update`
- `invoices.info`
- `creditNotes.info`
- An invoice number actually contains the bookyear, so from now on, you will see eg. `2018 / 27` instead of `27`.
This is reflected in the `invoice_number` property in the `invoices.list` and `invoices.info` endpoints.
#### 2018-10-30
- The top-level property `customer` was removed on all deal endpoints.
Earlier, this property could already be found under the `lead.customer` property.
If you were still using the `customer` property, just wrap it in an object under a `lead` key.
- The `contacts.list` & `companies.list` endpoints used to give back an object under the `address` key.
This object is now returned under the `primary_address` key.
### Stay informed
You can follow our API progress and ongoing proposals via our [API Blueprint GitHub repository](https://github.com/teamleadercrm/api).
# Group General
## Departments [/departments]
Departments are used to split quotations and invoices for different legal entities or within one organisation.
*Required scopes: `departments`*
### departments.list [GET /departments.list]
Get a list of departments.
+ Request (application/json)
+ Attributes (object)
+ filter (object)
+ ids: `92296ad0-2d61-4179-b174-9f354ca2157f`,`53635682-c382-4fbf-9fd9-9506ca4fbcdd` (array[string], optional)
+ sort (array, optional)
+ (object)
+ field (enum, required)
+ Members
+ name
+ order (enum, optional)
+ Members
+ asc
+ Default
+ (object)
+ field: `name`
+ order: `asc`
+ Response 200 (application/json)
+ Attributes (object)
+ data (array)
+ (object)
+ id: `67c576e7-7e6f-465d-b6ab-a864f6e5e95b` (string)
+ name: `Human Resources` (string)
+ vat_number: `BE0899623035` (string)
+ currency: `EUR` (string)
### departments.info [GET /departments.info]
Get details for a single department.
+ Request (application/json)
+ Attributes (object)
+ id: `92296ad0-2d61-4179-b174-9f354ca2157f` (string, required)
+ Response 200 (application/json)
+ Attributes (object)
+ data (object)
+ id: `67c576e7-7e6f-465d-b6ab-a864f6e5e95b` (string)
+ name: `Human Resources` (string)
+ vat_number: `BE0899623035` (string)
+ address (Address)
+ emails (array)
+ (object)
+ type: `primary` (enum)
+ Members
+ primary
+ invoicing
+ email: `info@piedpiper.eu` (string)
+ telephones (array[object])
+ type: `phone` (enum, required)
+ Members
+ phone
+ fax
+ number: `092980615` (string, required)
+ website: `https://piedpiper.com` (string)
+ currency: `EUR` (string)
+ iban: `BE12123412341234` (string)
+ bic: `BICBANK` (string)
+ fiscal_regime: `RF01` (string, nullable)
## Users [/users]
Users are co-workers in a Teamleader account.
*Required scopes: `users`*
### users.me [GET /users.me]
Get the current authenticated user.
+ Response 200 (application/json)
+ Attributes
+ data (object)
+ id: `cb8da52a-ce89-4bf6-8f7e-8ee6cb85e3b5` (string)
+ account (object)
+ type: `account` (string)
+ id: `0fc55513-7f68-4865-aba0-de5da9e4e43d` (string)
+ first_name: `John` (string)
+ last_name: `Smith` (string)
+ email: `john@teamleader.eu` (string)
+ telephones (array[Telephone])
+ language: `nl-BE` (enum)
+ Members
+ da-DK
+ de-DE
+ en-GB
+ es-ES
+ fi-FI
+ fr-FR
+ it-IT
+ nb-NO
+ nl-BE
+ nl-NL
+ pl-PL
+ pt-PT
+ sv-SE
+ tr-TR
+ function: `Sales` (string)
+ time_zone: `Europe/Brussels` (string)
+ preferences (object)
+ invoiceable: true (boolean)
### users.list [GET /users.list]
Get a list of all users.
+ Request (application/json)
+ Attributes (object)
+ filter (object, optional)
+ ids: `cb8da52a-ce89-4bf6-8f7e-8ee6cb85e3b5`,`f8a57a6f-dd1e-41a3-b8d3-428663f1d09e` (array[string], optional)
+ term: `John` (string, optional) - Filters on first name, last name and email
+ status (array[enum], optional) - Filters on status
+ Members
+ active - Filters on active users
+ deactivated - Filters on deactivated users
+ sort (array, optional)
+ (object)
+ field (enum, required)
+ Members
+ name
+ order (enum, optional)
+ Members
+ asc
+ Default
+ (object)
+ field: `name`
+ order: `asc`
+ page (Page, optional)
+ Response 200 (application/json)
+ Attributes (object)
+ data (array)
+ (object)
+ id: `cb8da52a-ce89-4bf6-8f7e-8ee6cb85e3b5` (string)
+ account (object)
+ type: `account` (string)
+ id: `0fc55513-7f68-4865-aba0-de5da9e4e43d` (string)
+ first_name: `John` (string)
+ last_name: `Smith` (string)
+ email: `john@teamleader.eu` (string)
+ telephones (array[Telephone])
+ language: `nl` (string)
+ function: `Sales` (string)
+ status: `active` (enum)
+ Members
+ active
+ deactivated
### users.info [GET /users.info]
Get details for a single user.
+ Request (application/json)
+ Attributes (object)
+ id: `cb8da52a-ce89-4bf6-8f7e-8ee6cb85e3b5` (string, required)
+ Response 200 (application/json)
+ Attributes
+ data (object)
+ id: `cb8da52a-ce89-4bf6-8f7e-8ee6cb85e3b5` (string)
+ account (object)
+ type: `account` (string)
+ id: `0fc55513-7f68-4865-aba0-de5da9e4e43d` (string)
+ first_name: `John` (string)
+ last_name: `Smith` (string)
+ email: `john@teamleader.eu` (string)
+ telephones (array[Telephone])
+ language: `nl-BE` (enum)
+ Members
+ da-DK
+ de-DE
+ en-GB
+ es-ES
+ fi-FI
+ fr-FR
+ it-IT
+ nb-NO
+ nl-BE
+ nl-NL
+ pl-PL
+ pt-PT
+ sv-SE
+ tr-TR
+ function: `Sales` (string)
+ time_zone: `Europe/Brussels` (string)
+ status: `active` (enum)
+ Members
+ active
+ deactivated
## Custom Fields [/customFieldDefinitions]
Custom fields are used to add additional data/properties to entities within Teamleader.
### customFieldDefinitions.list [GET /customFieldDefinitions.list]
Get a list of all the definitions of custom fields.
+ Request (application/json)
+ Attributes (object)
+ page (Page, optional)
+ sort (array, optional)
+ (object)
+ field (enum, required)
+ Members
+ label
+ context
+ order (enum, optional)
+ Members
+ asc
+ desc
+ Default
+ (object)
+ field: `label`
+ order: `asc`
+ Response 200 (application/json)
+ Attributes (object)
+ data (array)
+ (object)
+ id: `74855f4a-2b61-429c-81d8-c79ad3675a76` (string)
+ context: `contact` (enum)
+ Members
+ contact
+ company
+ deal
+ project
+ milestone
+ product
+ invoice
+ subscription
+ ticket
+ type (enum)
+ Members
+ single_line - Single line text
+ multi_line - Multiline text
+ single_select - Single selection - has configuration
+ multi_select - Multiple selection - has configuration
+ date - Date
+ money - Money
+ auto_increment - Automatically incrementing field
+ integer - Integer
+ number - Number
+ boolean - Yes/No
+ email - Email address
+ telephone - Phone number
+ url - URL
+ company - Company
+ contact - Contact
+ product - Product
+ user - User
+ label (string)
+ group (string)
+ required: false (boolean)
+ configuration (object, optional)
+ options: foo, bar (array[string])
+ extra_option_allowed: true (boolean)
### customFieldDefinitions.info [GET /customFieldDefinitions.info]
Get info about a specific custom field definition.
+ Request (application/json)
+ Attributes (object)
+ id: `9c64570b-4ec1-4e03-9662-af904f78f7fa` (string, required)
+ Response 200 (application/json)
+ Attributes (object)
+ data (object)
+ id: `57e851e2-3d3b-4523-82f8-fe77df5a5d6c` (string)
+ context: `contact` (enum)
+ Members
+ contact
+ company
+ deal
+ project
+ milestone
+ product
+ invoice
+ subscription
+ ticket
+ type (enum)
+ Members
+ single_line - Single line text
+ multi_line - Multiline text
+ single_select - Single selection - has configuration
+ multi_select - Multiple selection - has configuration
+ date - Date
+ money - Money
+ auto_increment - Automatically incrementing field
+ integer - Integer
+ number - Number
+ boolean - Yes/No
+ email - Email address
+ telephone - Phone number
+ url - URL
+ company - Company
+ contact - Contact
+ product - Product
+ user - User
+ label (string)
+ group (string)
+ required: false (boolean)
+ configuration (object, optional)
+ options: foo, bar (array[string])
+ extra_option_allowed: true (boolean)
## Work Types [/workTypes]
Work types define the type of work for events or time tracking. Hourly rates can be added to work types, so that the work can be billed to a customer.
### workTypes.list [POST /workTypes.list]
Get a list of all work types, sorted alphabetically (on their name).
+ Request (application/json)
+ Attributes (object)
+ filter (object, optional)
+ ids: `6e342192-76d4-4b26-b1d7-e24df46bf603`,`1652ab6f-ad24-4f5c-a2fc-c6a30693a930` (array[string], optional)
+ page (Page, optional)
+ sort (array, optional)
+ Default
+ (object)
+ field: `name`
+ order: `asc`
+ Response 200 (application/json)
+ Attributes (object)
+ data (array)
+ (object)
+ id: `811a5825-96f4-4318-83c3-2840935c6003` (string)
+ name: `Planning` (string)
# Group CRM
## Contacts [/contacts]
Contacts are physical entities who are added to your CRM database. Contacts might be linked to one or more companies.
*Required scopes: `contacts`*