Jobcast Social Recruitment App API

Request Formats

Retrieving Resources with HTTP GET

Example:

GET https://app.jobcast.net/api/v1.0/jobtypes HTTP/1.1
Host: app.jobcast.net
Connection: keep-alive

You can easily test GET requests by entering the URI in your web browser:

https://app.jobcast.net/api/v1.0/jobtypes

Creating or Updating Resources with HTTP POST and PUT

To create or update a resource, make an HTTP POST or PUT request with JSON in the body of the request. The JSON format is resource specific and not all resources support POST and PUT, so please refer to the Resources section for more info.

Be sure that the HTTP Content-Type starts with application/json, for example:

application/json; charset=UTF-8

Example:

PUT https://app.jobcast.net/api/v1.0/jobs/17082 HTTP/1.1
Host: app.jobcast.net
Content-Length: 31
Consumer-API-Key: a146471f-8e39-4e96-868f-19b9556a8297
User-API-Key: 0b52904c-1cf2-4572-8603-58d7673a1441
Content-Type: application/json; charset=UTF-8

{"title":"Mechanical Designer"}

Deleting Resources with HTTP DELETE

To delete a resource, make an HTTP DELETE request to the resource URI. Not all resources support HTTP DELETE, so please refer to the Resources section for more info.

Example:

DELETE https://app.jobcast.net/api/v1.0/jobs/17082 HTTP/1.1
Host: app.jobcast.net
Consumer-API-Key: a146471f-8e39-4e96-868f-19b9556a8297
User-API-Key: 0b52904c-1cf2-4572-8603-58d7673a1441

HTTP Method Overriding

If your HTTP client does not support PUT or DELETE requests, you can use HTTP method overriding. It works as follows:

  • We will look for a X-HTTP-Method-Override parameter in the following places (ordered by priority):
    1. HTTP Header
    2. Query String
  • If the original request is anything other than POST, X-HTTP-Method-Override will be ignored.
  • If the X-HTTP-Method-Override value is PUT or DELETE, that value will be used as the HTTP verb.

Example:

POST https://app.jobcast.net/api/v1.0/jobs/17082 HTTP/1.1
Host: app.jobcast.net
X-HTTP-Method-Override: DELETE
Consumer-API-Key: a146471f-8e39-4e96-868f-19b9556a8297
User-API-Key: 0b52904c-1cf2-4572-8603-58d7673a1441