Resources
Glossary
The terms used across the AdQuest documentation.
On this page
Terms
| Term | Meaning |
|---|---|
| Platform | Your app, registered in AdQuest. It owns the API keys and settings. |
| Public API key (aqk_) | Identifies your platform in browser and SDK requests. Safe to expose. |
| Secret Key (aqs_) | Lets your backend create participant sessions. Keep it on your server. |
| Embed URL | The hosted SDK address for your platform, https://sdk.adquest.batriders.ir/{publicId}. It is not a secret. |
| Participant | One signed-in user of your app who takes part in quests. |
| external_user_id | Your own stable ID for a participant. |
| Participant session | A short-lived identity your backend creates for one participant. |
| Participant token | The credential from a participant session. It lets the widget or client act as that participant until it expires. |
| Quest | A task a participant completes to earn tokens. |
| Quest format | The kind of task: video, banner, survey, visit, event, profile, referral, streak or custom. |
| Tokens | The reward currency participants earn from quests and spend on lottery entries. |
| Settlement | AdQuest’s server-side confirmation that a completion was valid and the reward was granted. |
| Reservation | A place held for one participant's attempt at a quest, with a server deadline. It is released if the attempt expires or is rejected and becomes the spend when the completion settles. |
| Lottery, entry, claim | Participants spend tokens to enter a lottery. A winner submits a claim to receive the prize. |
| Webhook | A signed HTTPS notification AdQuest sends to your backend, such as quest.completed or lottery.winner. |
| Where AdQuest may appear | The website addresses and app package name a publisher allows for a platform. When it is set, requests from anywhere else are refused. |
| Host context | Optional profile and permission data your backend sends when it creates a session. |
| Bridge | The postMessage protocol between your page or native app and the hosted embed. |