Imported Google Group message.
Date:Tuesday, 7 July 2015 18:45:10 UTC+1.
1) The main issue is that the call does not seem to work.
To create a client you don't need to target the listen path, this is only for the specific token authorisation endpoints, you can just target /tyk /* at the root level
Do not use the Authorize token, this is for the advanced API (documented on the site).
To create a client you need to target the node and use the Tyk secret defined in the Tyk.conf file.
2) I noticed in the Dashboard calls, they do not call the OAuth create call but instead call some dashboard call.
OAuth clients are stored with the node not in the dashboard (to minimise database calls, the node can operate without mongo once it starts), the API requests you see the dashboard make are to an internal API wrapper that actually talks to the node and the ID you see is the internal API ID (objectID) in Mongo.
The UI never directly talks to the nodes, everything happens via the advanced API.
3) What is the dashboard key ('Tyk Dashboard API Access Credentials') for under a user's details? I assume it would work for
Dashboard Advanced api calls but it seems that that is a different value when I see those calls being made in the dashboard UI.
The UI uses a separate session token to access the advanced API (makes it easier to handle auth and various other session issues, whereas the token associated with a user in the profile is always stateless). The credentials you see are for the advanced management API and would work just as well as the one the dashboard UI uses.
Let me know how you get on