Turns out that my trial and error on Postman worked.
I used my public key as the username and my private key as the password using Basic Authentication.
Why does your documentation not specify this very simple information?
My site is broken:
https://trisys.api.oneall.com/
{"response":{"request":{"date":"Wed, 17 Apr 2019 17:23:18 +0200","resource":"\/","status":{"flag":"error","code":404,"info":"We are really sorry, but the resource you are trying to access does …
This does not always work!
It works great on login where I always redirect manually, however when inside another part of the application where I have no UI, something is requesting a redirect and causing the Chrome event window.onbeforeunload to fir…
My ultimate aim is to drive everything from my own Javascript without using the oneall social buttons at all. This gives me more flexibility to build in my own specific business logic.
I figured this out. The connection_token should be sent to our own Web API and used with the API key and secret key as Basic Authorisation to GET from "https://trisys.api.oneall.com/connections/" + connection_token + ".json";
This file stream contai…
I assume that at this point I must in fact send the connection token to my own server via my own web API in order to then use your ReST API to query the connection, as this is a more secure process than connecting from the client exposing my API key?