What are APIs In Zonka Feedback?

API (Application Programming Interface) in simple terms, allow applications to talk to each other. Zonka Feedback has Use Ready-to-use Integrations with apps like Mailchimp. Mailchimp is a popular Email Gateway and is ideal for low to high volume email sends. Expand the capabilities of the platform with the use of Open API Access.
Application Programming Interfaces (APIs) allow applications to interact and share data.

Introducing a Better Way to Create Survey Emails and send them through APIs.

Zonka Feedback's REST APIs lets you to query and get requested data in JSON format using GET, POST, PUT or DELETE HTTP methods. Zonka's API documentation is organized by API endpoints and examples are shown for each of the endpoints which enables you to access data from different datasets associated with your Zonka account.

Where do you get your API keys in your Zonka Feedback account?

API Authorization Token/API Key : This key is a unique identifier used to authenticate a user, developer, or calling program to an API. The Auth Token is used to access Zonka Feedback APIs for your account. This Auth Token is associated with your account and Email Address, and can be used to access data associated with your account only.

This is 32 characters long alphanumeric code which you can find in your settings, please follow the steps below to access your API Authorization Token:

  1. Navigate to 'Settings' from the left bottom corner.
  2. Click on the developer drop down, and choose API.
  3. You find you API Authorization Token.

API tab is only accessible to Admin users within the Zonka account. The auth token will have the entire scope of the Admin user and can be used to access all datasets associated with the account.

Once you have generated an Auth Token and wish to generate a fresh token then you can do so by clicking Regenerate Token. Please note that the new token will make the previous token invalid and you will need to reconfigure your authentication to use APIs.

The base URL for accessing the API is `https://app-us1.zonkafeedback.com`

Ordering your API:

1. Decide your action - What are your actions or endpoints? Will you be using the API for sending or pulling out response data, or any other reason?

2. Decide the structure of your API requests - What are you sending Properties or metadata to Zonka Feedback? What language will you be using? Will there be any tim delay?

3. Know your triggers - When are you triggering the survey? 1 months or 3 months or immediately to your customers?

4. Decide on survey frequency - How frequently will you be calling this action or endpoint?

5. Know the properties of your request - If triggering survey requests, know what all information you can pass about your customer.

Purpose of Email Gateways:

An Email Gateway allows a Zonka Feedback account to send Emails to your customers without any human interventions or manual tasks.
Most emails are eventually routed to your customer's email addresses. By this integration you are able to:

  1. Email Logs: Get to know the number of Emails you have sent and the number of people who responded back. Get to know in detail about Email Logs.
  2. Speed: Delivering Emails to your clients is important. But it’s even more important is that you do so in a quick and timely manner. This can be achieved through integrations.
  3. More Accessibility: Emails are so effective and is known to be one of the best medium to communicate.

Example:
1. Food Delivery Scenario
Let's assume you have signed in with your email address and placed an order in a website ABC. Website ABC registers you as a customer in their database. Now you have integrated your Zonka Feedback account and Website ABC using APIs. Post the delivery after an hour time, they get an Email survey to the registered email id. This is done through integration without nay manual action.

2. Airlines Scenario
Let's assume you are traveling in an airlines and post your flight after 2 hours delay you would get an survey triggered to your email id. This can be done through integration without any human interventions.

In the above 2 scenario's the data GET action is done.

Did this answer your question?