To authenticate requests using Sunshine Conversations APIs, you can use either Basic authentication or JSON Web Tokens (JWTs). Both methods require an API key. Basic authentication involves using the API key directly, where the Key ID acts as the username and the secret key as the password. For JWTs, you sign tokens with an API key, and the Key ID is included in the JWT header as the 'kid' property, while the secret signs the JWT.
It's important to note that API keys are not as secure as authentication tokens, so it's crucial to follow best practices for securely handling credentials in production. For more details, you can refer to theAPI Authenticationsection.
Creating and sharing an API key for the Conversations API involves a few steps. First, a Zendesk administrator must create the API key and share it with the developer. You can store up to 10 keys at a time. To create an API key, go to the Admin…
The Conversations API key is intended for app-level authentication, while the Integrating Conversations API key is specific to a conversation integration. This distinction is important because the Conversations API key is used for server-to-server…
To access the Conversations API page, you need to be on a Zendesk Suite Professional plan or above, and the Zendesk Agent Workspace must be activated. This access is necessary to create and manage API keys for Sunshine Conversations. If you require…
Deleting an unused API key in Zendesk is straightforward. Navigate to the Admin Center, click on 'Apps and integrations' in the sidebar, then select 'APIs > Conversations API'. Hover over the key you wish to delete, click the options menu, and…
If you can't see the Conversations API option in Zendesk, it might be because you don't have a Sunshine Conversations account. The Conversations API is available only if you have this account. If you need assistance connecting it to your Zendesk…