Hub Planner API Documentation
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
Sections Updated Text Explanation Jul 31, 2018
.gitignore initial source deploy Dec 1, 2014 added vacation to main file Jul 24, 2018

Hub Planner API

Welcome to the Hub Planner API. The Hub Planner API provides programmatic access to the following Sections

You can use the API to integrate Hub Planner with your own third party applications or generally integrate with your existing back-office setup.

Zapier Integration

We offer an integration with Zapier. Please Visit Here to get access.

API Support

If you have a question about using the API or have noticed an error or omission in the documentation. Please feel free to open an issue on GitHub with your question and we will attend to it.

If you have any direct implementation issues, please contact the tech team at the following address and add API as as the Subject.

API Updates and Changes

We will be managing the API via GitHub, so please watch the Hub Planner API repository to receive email notification of updates to the API documentation.


If you've built something interesting with the Hub Planner API, made a wrapper for a certain code language or integrated with a third party software you would like to share or think will help others, then please let us know at

API Data Formats

Hub Planner API is a RESTful API that uses HTTP requests and returns JSON for all responses.

All URLs start with the root URL:

Content-Type and Accept must be defined in the header of all requests.

GET resource/123
Accept: application/json
Content-Type: application/json

Please note that all requests to the Hub Planner API must be made over HTTPS.


Most of the above areas can be paginated using url parameters limit and page. By default the limit is 0, which means unlimited. In the future unlimited listings will be disabled and the results will need to be paginated, so we suggest adding support for pagination as soon as possible.

The example call to make use of pagination looks like this:

GET /project?page=0&limit=20

Which will paginate endpoint with 20 results per page. Pages start numbering with 0. If you want to get all results you should loop trough pages until you reach page with less than requested amount of elements(in this example less than 20).

The endpoints that can be paginated in most areas are GET /areaName and POST /areaName/search.

Sorting results

Most of the endpoints can be sorted ascending or descending based on some of the properties. Documentation for each area you have access to lists sortable fields in the property table. Results can be sorted for GET /areaName and POST /areaName/search requests.

To sort the data add sort parameter to the url, followed by field you want to sort by. Prefix the property with minus sign(-) to sort in descending order. For example:

GET /projectGroup?sort=-name

Will sort the project groups in descending order based on their names.

You can chain multiple sort arguments to create more advanced sort results. For example:

GET /projectGroup?sort=-groupType&sort=name

Will first sort project groups by their group types in descending order, then sort each group type alphabetically by name. Sample response(with unnecessary properties ommited):

      "name":"Eric's Projects",
      "name":"Greg's Projects",
      "name":"Rudolf's Projects",
      "name":"Active Projects",
      "name":"Archived Projects",
      "name":"Floating projects",
      "name":"Pending projects",
      "name":"Planned projects",

It's suggested that you use sort argument along with pagination.

User Agent Identification

Remember to write your application carefully. In case of abuse you may be blocked, disallowing further API access. As an act of courtesy, please provide User-Agent strings denoting your application.

User-Agent: My Hub Planner Import App (


Hub Planner API is authenticated with a OAuth 2.0 Bearer Token.

You must supply an Authorization header with the token for all requests.

Authorization: xxx

Where xxx is Your generated API key. Do not provide Bearer keyword before API key in the header.

You must enable API access and generate your API key in order to use the Hub Planner API. The API key is available in All Accounts with Administrator privileges and higher. To generate your API key and enable the API login to your Hub Planner account and navigate to

Settings -> API

Here you can generate your key for different rights and enable access.

There are 2 types of API keys you can generate.

  • Read Only
  • Read & Write

Please note if you decide to disable access to the API. All API access will be revoked for all generated keys. The generated keys should be considered as sensitive as passwords and must not be shared or distributed to untrusted parties.

Error Codes & Responses

Overview of possible HTTP status codes

Code Text Description
200 OK Success.
201 OK Created.
400 Bad Request The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
401 Unauthorized The request requires user authentication @Authentication
403 Forbidden The request is understood, but it has been refused or access is not allowed.
404 Not Found The URI requested is invalid or the resource requested, such as a user, does not exists.
429 To Many Requests This status code indicates that the user has sent too many requests in a given amount of time ("rate limiting"). We currently allow 2 requests / second per account.
500 Internal Server Error Something unexpected broke. Please raise an issue so we can investigate your problem.
502 Bad Gateway Hub Planner API is down or temporary not accessible.