

Most collection APIs paginate their results.
#BASECAMP 3 CALENDAR VIEW CODE#
You'll receive a 415 Unsupported Media Type response code if you don't include the Content-Type header. Alternatively you can send Accept: application/json. This means that you have to send the Content-Type header Content-Type: application/json charset=utf-8 when you're POSTing or PUTing data into Basecamp. The style is no root element and snake_case for object keys.

Pagination is performed via the Link and X-Total-Count headersĪll URLs start with.We require OAuth 2.0 for authentication-no more Basic authentication.Here are some notable changes for the Basecamp 3 API: If you've used a previous version of the Basecamp API, you need to adapt your integration code.

The core ingredients are the same, though: Basecamp 3 is a REST-style API that uses JSON for serialization and OAuth 2.0 for authentication. All integrations will start fresh with the new API. The Basecamp 3 API is not compatible with the Basecamp Classic API or the Basecamp 2 API. We're happy to have you! Compatibility with previous Basecamp APIs Welcome to the Basecamp 3 API! If you're looking to integrate your application with Basecamp 3 or create your own application in concert with data inside of Basecamp 3, you're in the right place.
