Authentication for Advisor endpoints
Once we’ve registered your business on our platform we’ll provide you with a client ID and a client secret. In the future, OAuth may be worthwhile, however all Advisor API calls are currently authenticated using HTTP Basic Authentication with these 2 values.
Client Id: kaGA65sIl79IdXxr3lnGs7J2C9CywQtJ
Client secret: ueeKzJOEh0fh6Dh8
The Authorization header is constructed as follows:
Client Id and client secret are combined into a string “client id:client secret”.
The resulting string literal is then encoded using Base64.
The authorization method and a space, i.e. “Basic “ is then put before the encoded string.
For example, if the user agent uses ‘kaGA65sIl79IdXxr3lnGs7J2C9CywQtJ’ as the client Id and ‘ueeKzJOEh0fh6Dh8’ as the client secret then the header is formed as follows:
- kaGA65sIl79IdXxr3lnGs7J2C9CywQtJ:ueeKzJOEh0fh6Dh8
- a2FHQTY1c0lsNzlJZFh4cjNsbkdzN0oyQzlDeXdRdEo6dWVlS3pKT0VoMGZoNkRoOA==
- Authorization: Basic a2FHQTY1c0lsNzlJZFh4cjNsbkdzN0oyQzlDeXdRdEo6dWVlS3pKT0VoMGZoNkRoOA==
Helpful links:
http://en.wikipedia.org/wiki/Basic_access_authentication