Skillhive Developers

Skillhive API

Skillhive API Documentation

About Skillhive API

Skillhive API is designed to be flexible and developer friendly. It's designed around RESTful principles.


We do our best not to brake backwards compatibility, but this can happen in some unforeseen circumstances. Therefore, we provide the possibility to define which version of the API you are accessing and get the contents in the format you want.

You can define the version using Content-Type HTTP header as follows:


Where YYYYMMDD is the version (based on date, obviously) you requested. You don't have to define the content-type, then you will just get the latest version.

Browsing the API

Skillhive API URI endpoints are designed to be as permanent as possible. But things change and we don't know what our API will evolve into. Keep this in mind and don't hardcode API endpoints into your application. Instead, ask the initial endpoints through the API.

For exapmle, calling the root of the api at /api/ will return the current user, and the user object includes the URI for the user. Almost all objects include a resources object, which includes URI endpoints for resources belonging to that object.

For instance, the user object includes


Use the URI endpoints defined in the resources object and don't harcode the endpoints. If you want to get the user's skills, for instance, don't hardcode the uri as /api/user/:user_id/skill/ but use the URI defined in resources instead.

Of course, hopefully we will never have the need to change our URI format, but you never know. It's good to get this right from the start.

Notice that all URIs include a trailing slash.


All responses from Skillhive are returned in JSON format.


We embrace the HTTP specification and set the status codes, content types and other HTTP headers accordingly. Almost all responses have some common elements in them. These are described below.


All listing responses through the API will be in the following format. Here's an example of what a call to /api/user/?limit=20&offset=0 could look like.

  "limit":20,                              // Current limit, defaults to 20
  "offset":0,                              // Current offset, defaults to 0
  "total_count":312,                       // Total number of objects
  "previous":null,                         // Pagination, previous set
  "next":"/api//user/?offset=20&limit=20", // Pagination, next set
  "collection": [                          // The user collection


Almost all objects will include some common elements. Here's an example of a user object:

  "id":12345,               // All objects have an `id`
  "uri":"/api/user/12345/", // Object URI is always included as `uri`
  "created_at" :            // Timestamps telling when the object was created...
  "updated_at" :            // ... and when it was modified.

Most objects include a resources object which includes URIs to other resources belonging to this object. For example, the user object include skills and colleagues in the following format


Using these API endpoints it's easy to get extra resources related to the object.


All objects include timestamps when they were created and last updated. Timestamps are always named as created_at and updated_at. Here's an example of a timestamp hash:

"created_at": {
  "date": "Thu, 30 Jan 2014 16:01:07 +0200",
  "friendly_time": "33 days ago",
  "date_local": "2014-1-30"

The timestamps hash includes the full date, a friendly_time string and a localized date_local string for the date. date is formatted in the RFC 2822 format which is perfect for JavaScript, for instance. Notice, that date_local is formatted based on site language setting in Skillhive. For instance, in the above example date_local would be 30.1.2014 if Finnish had been chosen as the current language. friendly_time is also translated based on the language setting in Skillhive.

Fetch URI endpoints and current user

Endpoint: /api/

This is the perfect starting points for using the API. Calling /api/ will return the current user object and the URI endpoints for our API.

Method Action Parameters
GET Fetch URI endpoints N/A

An example of a return response:

    "name":"Test User",
    "description":"I'm just a PHP programmer.",
    "job_title":"PHP Coder.",
    "location":["Helsinki", "Finland"],
    "department":["Research and Development", "Intunex HQ"],
    "phone":"412 4214 421421412",
    "mobile":"+358 40 123 4567",
    "created_at" :
    "updated_at" :