UseResponse is a complex platform to support customers and social CRM, but if you use other systems for project management, invoicing, billing, hosting, you can enhance your experience with customers by integrating our Restful API into your platform.
When making RESTful API requests you need to be prepared to handle returned HTTP response codes.
With UseResponse API you can use following REST commands over http using json: POST, GET. PUT, DELETE
All requests should be done to your platform (resource URL) preferably using https protocol. Make sure to use cURL to make requests, SDK or from your command line.
Here is how we refer to the specific resource:
It means that you need to prepend your custom domain before the request that is similar to the example below:
You can get the domain name from your profile api settings that is under options.
All requests are done in json format. Examples of requests and responses are stated in each section of documentation.
Authentication and Tokens
In order to make any requests to UseResponse API, you'll need to authorize your requests by providing valid API key. If guest API is available, you can make requests without providing any api key.
General API settings could be managed in Administration » System » API where you have ability to turn off api, use guest api, and set permissions to use it only for specific admins and agents.
To fetch the data, you need to have permissions that are defined by role in the system. For example, if you'll use guest api, you would get only those information, that is available to guest in the community.
API Keys could be taken and regenerated at User Profile - Options - API Settings. You can also turn off keys for specific users.
curl -i -H "Accept: application/json" -H "Content-Type: application/json" -X GET <a href="https://domain.com/api/3.0/users/search.json?apiKey=<your_api_key>&role=user">https://domain.com/api/3.0/users/search.json?apiKe...</a>
By default, returned number of records per page could be 50. You can change the number of retrieved records with COUNT parameter.
The returned request will include total number of objects, objects per page, number of pages (first, next, last)
Success or error codes returned by UseResponse API would give you explanation about the status of your request in case you'll experience any issues:
|204||No Content||Request is successful, but no results were found|
|400||Bad Request||Invalid request and/or request parameters|
|401||Bad Authentication Data||Authentication is required in order to retrieve data. Either invalid api key or wrong format of api key|
|403||Forbidden||API request is prohibited due to lack of permissions|
|404||Not Found||When the requested resource is not found (resource doesn't exist or 401/403 security error codes are returned). For example API request was made on invalid URL.|
|405||Method Not Allowed||The requested method is not allowed. For example API request was made using DELETE method, but resource accepts GET or POST only.|
|409||Conflict||Whenever a resource conflict would be caused by fulfilling the request or duplicated entries|
|500||Internal Server Error||The general catch-all error when the server-side throws an exception|
|503||Service Unavailable||API is interface unavailable or disabled|
API Clients - SDK
API client on PHP will help you quicker implement UseResponse API and optimizes working with data using ready methods to work with tickets, topics, users, etc.
Client could be added using composer or as standalone autoloader.
Archive also includes examples of making typical API requests in order to understand how it works located at /src/Sdk/Examples