#BASECAMP 3 CALENDAR VIEW HOW TO#
#BASECAMP 3 CALENDAR VIEW FULL#
#BASECAMP 3 CALENDAR VIEW CODE#
#BASECAMP 3 CALENDAR VIEW FREE#

There are two phases of work when you start a new product. We’re working on a new product right now, and we’re following the same approach we used to build Basecamp 3 and Basecamp 2 before it.

#BASECAMP 3 CALENDAR VIEW HOW TO#

There’s a new appendix in the book now to answer this question: How to Begin to Shape Up: New versus existing products. People in my book club love all the principles, but they had one question: How did they build Basecamp 3 doing this? It seems like all the practices are for adding features to an existing product. To talk with us and other developers about the API, post a question on StackOverflow tagged basecamp or open a support ticket.Here’s a common question that’s coming up about Shape Up, our new book on product development:

#BASECAMP 3 CALENDAR VIEW FREE#

Also, feel free to fork these docs and send a pull request with improvements! If you have a specific feature request or if you found a bug, please open a support ticket. Please tell us how we can make this API better.

#BASECAMP 3 CALENDAR VIEW FULL#

See the list of data responses at the end of the page for a full description of the format of that response type. : Indicates content from the response has been elided for brevity in documentation. #: Indicates text that should be replaced by your own data.

To make things easier to understand, the following notation is used: If SSL is enabled for your account, ensure that you're using https. The Location header will contain the correct URI.

SSL UsageĪ non-SSL request made against an account that has SSL enabled (and vice versa) will receive a '302 Found' response. If you exceed 60 requests in a minute, your client will need to wait a full minute to resume. It's especially important to set an identifiable User-Agent header.

No User-Agent header: 60 requests per minute.

Rate limits in effect as of August 2014, per source IP and Basecamp account: Retrying the request before the time window has elapsed will flag your API client for flooding. Wait until that time has elapsed and resume your requests. When you exceed a rate limit, you'll get a 503 or 429 response with a Retry-After header indicating how many seconds to wait before trying again. If you make more requests than that in a minute, subsequent requests will be rate-limited for the following minute. For example, 100 requests within a minute. Design your API client to expect and properly respond when you encounter a rate-limited response.Ī rate limit is based on the number of requests made within a time window. Rate limitingĪPI requests are subject to rate limiting. Any other successful operation (like a successful query, delete, or update) will return a 200 status code. Note that, in general, if a request causes a new record to be created (like a new message, or to-do item, etc.), the response will use the '201 Created' status.

#BASECAMP 3 CALENDAR VIEW CODE#

If a request succeeds, it will return a status code in the 200 range and often, an XML-formatted response. Need a sample of each XML blob will look like? Check out the Data Reference. (Hint: Press t to enable the file finder and type out the endpoint you need!) User-Agent: Fabian's Ingenious Integration made without an identifiable User-Agent are much more tightly rate-limited. Making a requestīe sure to set both the 'Content-Type' and 'Accept' headers to 'application/xml' to identify the request and response format. Read the Basecamp API Authentication Guide for more info on using OAuth. This allows users to authorize your application to use Basecamp Classic on their behalf without having to copy/paste API tokens or touch sensitive login info. If you're making a public integration with Basecamp Classic for others to enjoy, you can also use OAuth 2. Your API token can be found by logging into your Basecamp Classic account, clicking on the 'My Info' link in the upper-right, and then clicking the 'Show your tokens' at the bottom (under 'Authentication tokens'). This is secure since all requests in the new Basecamp use SSL. If you're making a private integration with Basecamp Classic for your own purposes, you can use HTTP Basic authentication. Wrote your own API wrapper? Feel free to open a pull request and add to this list! Authentication We've tried to make the API follow the REST principles as much as we can. Every resource, like Post, Comment, or TodoList, has their own URL and are manipulated in isolation. The Basecamp Classic API is implemented as vanilla XML over HTTP using all four verbs (GET/POST/PUT/DELETE). It is not compatable with the Basecamp 2 API or Basecamp 3 API.

Basecamp 3 calendar view