For specific use cases, it might be necessary to extend our Unified API. Chift provides two ways to do this:
  • Get raw data
  • Call custom endpoints
These features are designed to extend our unified API to meet unique integration requirements.
They enable direct communication with the native APIs of individual integrations, providing the flexibility to customize functionality and create tailored solutions for specific needs.

​
Raw data

You can use this feature to fetch the raw data of the API calls done to build the unified data. E.g. GET /pos/customers:
It will return next to the unified data (as always), a raw_data field with the endpoints called and the result. 
{
  "items": [
    {
      "id": "168390",
      "first_name": "Henry",
      "last_name": "Michel",
      "name": "Henry Michel",
      "phone": null,
      "email": null,
      "created_on": "2016-01-13T10:05:10+01:00",
      "addresses": [],
      "loyalty": 0,
      "birthdate": null
    },
    ...
  ],
  "page": 1,
  "total": 1005,
  "raw_data": {
    "customers?offset=9000&limit=1000": {
      "customers": [
        {
          "id": 24909902
          ...
        }
      ]
    }
  }
}
This gives you the possibility to extend the features you are building with Chift’s integrations.
Using the API Explorer, you have a checkbox to activate the “raw data” feature to test it out.
You can test this on your sandbox environment. Please contact your CSM to activate this into production.

​
Custom endpoints

You can use this feature to directly call a specific endpoint of a connector. E.g. For a POS connector, you want to call a route to give you the list of promotions of restaurants. This can be done as such:
GET /consumers/consumerid/pos/custom/name_of_endpoints_with_params
You need to add custom after the name of the unified api and the endpoint you are requesting. E.G. GET /consumers/consumerid/pos/custom/promotions Chift will manage the authentication as always and will pass the other parameters to the endpoint. You are responsible to pass all required params as needed for the specific route of the connector.
This is not yet implemented on all connectors. Please contact the support or your CSM if needed
You can test this on your sandbox environment. Please contact your CSM to activate this into production.