If you have issues with accessing the Platform API, use the following tips and steps to help you with troubleshooting:
- If your Telligent Evolution platform community uses Windows Authentication, then you'll need to send network credentials with your request.
- When not using Windows Authentication, the user account you're using to access the REST API must have an API key already created. If it doesn't have one, log into the site with that user account and go to Settings > User Settings > Site Options, then click Create and Edit Application Keys at the bottom of the page to create a key. Note: You need to remember this key to use it when you access the REST API.
- When generating the Rest-UserToken make sure you use your community username, and not the name of the API key.
- If using Single Sign On, the Telligent username may not be the same as the username you enter on your login page
- If you are using REST impersonation to perform actions for other users (that is, using it as a service account), the user account that you are using for REST API access must be assigned to a role that has the Site - Impersonate Users permission.
- The user account that you are using for REST API access must be in a role that has the Site - Access Web Services permission. By default only the Administrator role has this permission and the Everyone and Registered Users roles do not. If you want to allow a limited set of users to access Web services but do not want to make them administrators, you could create a new role called “Web Services Users” and assign the Site - Access Web Services permission to that role. Then you can add any users you want to grant Web service access to the role.
- If you are using REST impersonation to perform actions for other users (that is, using it as a service account), the user account that you are using for REST API access must be assigned to a role that has the Site - Impersonate Users permission.