Build applications, mash-ups using the powerful Huddle developer API.
What do I need to know before I start?
The Huddle API is built using HTTP standards. Developers should familiarize themselves with these standards and concepts before developing against the Huddle APIs.
How does authentication work?
Huddle use OAuth 2 for authentication on their APIs. Full documentation on the OAuth flow and details on getting an API token are available on our documentation on integrating using OAuth.
All API examples assume that you have already been issued an API token from the OAuth server. Once you have received a token, you can use it by placing it in the header as follows:
GET /someresource HTTP/1.1 Authorization: OAuth2 some-long-token-string
If the token is not present, is malformed, or has expired, you will receive a 401 not authenticated error. For information on refreshing your token or retrieving a new token, see the documentation on integrating using OAuth.
How do I get access to the Huddle API?
- Application name
- Company (if appropriate)
- Contact name, phone and address
- Contact email
- Redirect URI (see here)
- Is this a web application, a desktop application, or an application running on a device?
- Short description of your application
You should receive a confirmation of receipt of your request within one business day. We aim to process all requests within three business days.
What functionality does your API currently support?
The Huddle API currently provides extensive methods to work with files and folders, tasks, comments and people. We also provide a Changes API to allow you to efficiently query modifications to an object and its children.
See the API documentation for the full list. We’re constantly adding new methods so check back often.