Glia provides a robust set of APIs that allow for two-way data integrations with the Glia platform via secure REST API calls. This documentation provides information and examples for each of the available APIs delivered by Glia. These APIs allow clients to create integrations for areas of the platform such as Visitors, Operators, Engagements, Statistics, and Single Sign On. The APIs allow clients to keep Glia synchronized with their systems of record with minimal development effort.

This documentation is for Glia API v1 and includes example responses for each API method illustrating the attributes returned by that method. If you have any issues, requests or concerns with the documentation please contact our Customer Support team at support@salemove.com.

Current Version

The current API version is v1 and it must be explicitly requested via the Accept header.

Accept: application/vnd.salemove.v1+json

Schema

All API access is over HTTPS and accessed from the https://api.salemove.com endpoint. All data is sent and received as JSON. The only supported cryptographic protocol is TLS 1.2.

Blank fields are included as null instead of being omitted.

HTTP/1.1 200 OK
Date: Thu, 29 Jan 2015 11:44:37 GMT
Status: 200 OK
Connection: close
Content-Type: text/html;charset=utf-8
Access-Control-Allow-Origin: https://salemove.com
Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS, PATCH
Access-Control-Allow-Headers: *, Content-Type, Accept, AUTHORIZATION, Cache-Control, X-Salemove-Visit-Session-Id
Access-Control-Allow-Credentials: true
Access-Control-Max-Age: 1728000
Access-Control-Expose-Headers: Cache-Control, Content-Language, Content-Type, Expires, Last-Modified, Pragma
Content-Length: 0
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN

All timestamps use the ISO 8601 format.

YYYY-MM-DDTHH:MM:SSZ

Parameters

Many API methods take optional parameters. For GET requests, any parameters not specified as part of the path can be passed as an HTTP query string parameter. For POST, PATCH, PUT, and DELETE requests, parameters not included in the URL should be encoded as JSON with a content-type of application/json.

Client Errors

If the request is malformed, then the server responds with an error. The response contains a description of the error. In general, the response includes two attributes: namely, error which contains a short description of the error encountered; and a debug_message which contains a more detailed explanation of the error.

HTTP/1.1 400 Bad Request

[
  {
    "error": "BadRequest",
    "message": "Invalid api version used",
    "debug_message": "Invalid api version used. Make sure you set the 'Accept' header with API version e.g. 'application/vnd.salemove.v1+json'"
  }
]

HTTP Verbs

Where possible, the Glia APIs strive to use appropriate HTTP verbs for each action.

Headers

Along with the request, the following headers must be sent:

curl --request GET \
    --header "Authorization: Token $token" \
    --header "Accept: application/vnd.salemove.v1+json" \
    "https://api.salemove.com/operators"

Authorization

Operators must specify their API Token in the Authorization header. The API tokens are provided by the Site success manager.

curl --request GET \
  --header "Authorization: Token $api_token" \
  --header "Accept: application/vnd.salemove.v1+json" \
  "https://api.salemove.com/operators?site_ids[]=$site_id&include_offline=false"

Visitors must specify their access token in the Authorization header. This header can be acquired using either JS API or REST API when creating a new Site Visitor.

curl --request GET \
  --header "Authorization: Bearer $access_token" \
  --header "Accept: application/vnd.salemove.v1+json" \
  "https://api.salemove.com/visitor/visit"

Accept

Unless otherwise specified, all endpoints require Accept: application/vnd.salemove.v1+json header.

Cross Origin Resource Sharing

The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from any origin. More information about CORS is available in the CORS W3C Recommendation and in the intro to the HTML 5 Security Guide.

Pagination

GET /operators

Generates the output

  {
    "next_page": "http://api.salemove.com/operators?page=2",
    "last_page": "http://api.salemove.com/operators?page=3",
    "collection": [
      {
        "href": "http://api.salemove.com/operators/f42811bc-8519-4d33-bbb1-36d4555ecb0a",
        "attribute": "value",
        "...": "..."
      },
      {
        "href": "http://api.salemove.com/operators/c8b52f0b-ad05-4c71-8c98-5056f07c4d1a",
        "attribute": "value",
        "...": "..."
      },
    ]
  }

Some requests that return a large collection of items are paginated. The following parameters are supported:

For example, to fetch the second page of the Operators which the Token in the query is authorized to view, the parameter page should be set to a value of 2 (page=2) as shown below.

GET /operators?page=2

Link Header

The responses for collections that are paginated include an attribute next_page that points to the next page of items for the collection. In addition, the response includes a last_page attribute that points to the last page of the collection.