v2.0 Release

Official release of Content API v2.0. Introducing new API endpoints for accessing the details and 3D models associated with team collections. This release also includes updates to the v2.0 /myhuman endpoint, as well as additions to the error response messages.

General Updates

• All v2.0 API urls will require using /v2/ as the version number:

  • https://apis.biodigital.com/oauth2/v2/...
  • https://apis.biodigital.com/services/v2/content/collections/...

• New response error messages when making authorized requests to v2.0 API endpoints. Error response parameter definitions can be found in the Error Response section of an endpoint's reference page:

  • collection_endpoint_not_found
  • collection_endpoint_invalid

Updates to v2.0 /myhuman endpoint

• Response parameter content_url now uses /viewer/ as its url path. Url path /widget/ is no longer used for the content_url parameter.
• Response parameter content_description is no longer available.
• Response parameter content_group has been renamed to content_teams. The sub-parameters have also been renamed:
  group_id has been renamed to team_id.
  group_name has been renamed to team_name.
• Response parameter content_accessibility now uses string "team" for content that is associated with a team account. The string "group" will no longer be an option.

New team collection endpoints

• v2.0 /mycollections endpoint: returns a list of your team collections.
• v2.0 /mycollections/{id} endpoint: returns details for a specific team collection.
• v2.0 /mycollections/{id}/content_list endpoint: returns a list of the 3D models within a specific team collection.

New demo code examples

Adding 2.0 versions of our sample code applications. You can download the source code and run these demos locally as examples of making requests to the various Content API v2.0 endpoints. The demo applications are currently available in the following programming languages:

• .NET C#
• Java
• Node.js
• PHP
• Python
• Ruby