Create Download Link and Use it Later

Seamlessly integrate Anakage’s self-service portal with your omnichannel strategy for enhanced efficiency and secure access to solutions

At Anakage, we understand the importance of providing our clients with a seamless experience when accessing our solutions. That’s why we offer a self-service portal feature that allows our clients to easily access our solutions through any omnichannel.

By implementing this feature, clients can benefit from the flexibility and convenience of omnichannel integrations without compromising the security of their data. Our support team is always available to answer any questions or concerns about using the API self-service portal feature.

In summary, our self-service portal feature can be integrated with other omnichannels such as In-house Chatbots or existing Knowledge Base articles. Users can simply click on the provided link to download the solution file securely and conveniently.

Our API-based authentication enables clients to securely and conveniently download solution files using their solution number (sn). For added security, we recommend using strong and unique passwords when including authentication credentials in the request header.

During the deployment phase, our team at Anakage works closely with clients to implement this feature, which proves to be very helpful for clients who have in-house chatbots that are effective for short conversations but lack the capability to resolve complex endpoint issues. This feature enables clients to integrate our self-service portal with their existing knowledge base and other omnichannel platforms, providing a more comprehensive solution for their endpoint support needs.

(Optional Learning) Using API Endpoint /api/solutions/download to Download Solution Files with Basic Authentication

The API Endpoint /api/solutions/download can be used to download a solution file by providing its solution number (sn). To make a request, use a GET request with the sn parameter included in the query. Additionally, Basic Authentication is required in the request header with the authenticated user’s username and password.

If the solution number provided is valid and exists, the API will respond with the solution file in the response body. On the other hand, if the solution number is invalid or doesn’t match any existing solutions, the API will respond with a 404 Not Found error.

For example, if you want to download the solution with solution number 4, you can use the URL: https://example.com/api/solutions/download?sn=4

Don’t forget to include Basic Authentication with the appropriate username and password in the request header. You can modify the URL to include Basic Authentication in the format: https://username:password@example.com/api/solutions/download?sn=4

Ensure that the URL is URL-encoded if it contains any special characters or spaces.