The Doozy API is currently in closed beta. To request access, please email [email protected].
This guide walks you through calling the Doozy API from Make (formerly Integromat) to automate your reporting workflows.
Prerequisites
Before you begin, ensure you have:
- A Doozy account with API access enabled (see Authentication)
- A Doozy API key
- A Make account
Setting Up the HTTP Module
Make doesn’t have a native Doozy integration, so you’ll use the HTTP module to make API requests.
Create a New Scenario
Log in to Make and click Create a new scenario.
Add the HTTP Module
Click the + button and search for HTTP. Select Make a request.
Configure the Request
Set up the HTTP module with the following settings:| Field | Value |
|---|
| URL | https://api.doozy.live/v1/quizzes |
| Method | GET |
| Headers | Add a header (see below) |
Add a header:
- Name:
x-api-key
- Value: Your Doozy API key (
dzy_xxxxxxxx_...)
Test the Connection
Click Run once to test the connection. You should see a list of your quizzes in the response.
Example: Fetching Quiz Results
To fetch detailed results for a specific quiz:
| Field | Value |
|---|
| URL | https://api.doozy.live/v1/quizzes/{quizId}/report |
| Method | GET |
| Headers | x-api-key: your-api-key |
Replace {quizId} with the actual quiz ID from your Doozy dashboard.
Handling Pagination
For endpoints that return multiple items, you may need to handle pagination:
First Request
Make the initial request with your desired limit parameter:https://api.doozy.live/v1/quizzes?limit=25
Check for More Results
Check if the response has more items by looking at the has_more field.
Fetch Next Page
If there are more results, use the last item’s ID as the starting_after parameter:https://api.doozy.live/v1/quizzes?limit=25&starting_after=quiz_abc123
Use Make’s Iterator and Repeater modules to loop through paginated results automatically.
Storing Your API Key Securely
Instead of hardcoding your API key, use Make’s Data Stores or Variables to store it securely:
- Go to More → Keys
- Create a new key with your API key value
- Reference this key in your HTTP module headers
Error Handling
Add a Error handler route to your scenario to handle API errors gracefully:
- 429 errors: Add a Sleep module and retry
- 401 errors: Check your API key is valid
- 404 errors: Verify the resource ID exists
See Error Handling for a complete list of error codes.
Example Workflow: Weekly Quiz Report to Google Sheets
Schedule Trigger
Add a Schedule trigger to run weekly.
Fetch Quiz Report
Use the HTTP module to fetch /v1/quizzes/{quizId}/report.
Parse Response
Use the JSON module to parse the response data.
Add to Google Sheets
Use the Google Sheets module to append the data to your spreadsheet.