Beeline Connect API (2.0)

Connect API v2 provides 2 major improvements over Connect API v1:

1. XML & JSON support - you can specify the format of responses by sending Accept header in request: Accept: application/xml or Accept: application/json (default). The same goes for request payloads for PATCH and POST requests, which can be send in either XML or JSON format with appropriate Content-Type header (Content-Type: application/xml or Content-Type: application/json)
2. Leaner /workers responses for improved performance - by default listing workers returns only basic worker and engagement fields. This results in faster responses and smaller response size. If your integration requires fields that are not included by default, please refer to the documentation of following parameters of GET /workers query: includeEngagementReferences, includePersonalDetails, includeCustomFields.

Some entities are not yet supported in the v2 API - the list will be extended in future. See v1 API documentation for the list of entities supported in v1 API (XML only).