Prepare to use API
Using Desk Platform API, you can directly interact with the different types of resources which represent data associated with customer support activities in your Sendbird Desk. The Desk API is designed to use standard HTTP protocols and return
JSON payloads in response to HTTP requests and is internally implemented based on the
RESTful principles. While the native SDKs handle many of the requests and responses at the client-side, the Desk API adds flexibility and abilities to your service from the server-side.
Note: The Desk API is not designed for client side use. Use the corresponding Desk SDKs instead.
The base URL used for the Desk API is formatted as shown below:
To get your Sendbird application ID, sign in to your dashboard, select the application, go to the Settings > Application > General, and then check the Application ID.
A typical HTTP request to the Desk API includes the following headers:
- Content-Type: every request must include a
- SENDBIRDDESKAPITOKEN: an API key of your Sendbird Desk is required for Sendbird server to authenticate your API requests. You can use any of API keys in your dashboard under Settings > Desk > Credentials.
DO NOT send any Desk API requests from your client app. If your API token information is leaked in the process of exchanging data, you could lose all your data by malicious API calls.
If your request contains a file, you should send a Multipart request. To make that request, specify
multipart/form-data in the
Content-Type header, as well as a
boundary, which is a delimiter string that separates each data field.
When sending requests over HTTP, you should encode URLs into a browser-readable format. URL encoding replaces unsafe
non-ASCII characters with a
% followed by hex digits to ensure readability.
In the following URL, the value of the
agent_id parameter should be urlencoded. For example,
firstname.lastname@example.org should be urlencoded to
Therefore, your full request should be as below: