Kitetags API Overview — Authentication and Base URL
Get started with the Kitetags API. Learn how to generate an API key, authenticate requests, and understand the primary integration paths for NFC tap data.
How does Kitetags API authentication work?
All authenticated requests to Kitetags use an API key. You generate this key in the Kitetags dashboard.
How to generate an API key
- Log in to your Kitetags dashboard at kitetags.com.
- Navigate to Apps in the left sidebar.
- Click Generate API Key.
- Copy the key and store it somewhere safe. You will not be able to view the full key again.
How to use the API key
Include your API key in the Authorization header of every request:
Authorization: Bearer YOUR_API_KEY
What is the Kitetags API base URL?
All API requests use the following base URL:
https://api.kitetags.com/v1
What are the primary integration paths?
For most use cases, you will not need to call the API directly. Instead, Kitetags offers two event-driven integration paths that push tap data to your systems automatically:
| Integration | How it works | Best for |
|---|---|---|
| Webhooks | Kitetags sends a POST request to your endpoint on every tap | Custom backends, serverless functions, SaaS platforms with webhook support |
| Zapier | Kitetags triggers a Zapier zap on every tap | No-code automations, connecting to Google Sheets, Slack, CRMs, and 6,000+ apps |
The API key is required when setting up the Zapier integration to authenticate your Kitetags account within the Zapier platform.
What are the API rate limits?
API requests are rate-limited based on your subscription plan. If you exceed your limit, the API returns a 429 Too Many Requests response. Contact Tagstand support if you need higher limits for your use case.
Next steps
- Set up a webhook endpoint to receive tap events on your server
- Connect Kitetags to Zapier for no-code automations
- Browse integration examples for real-world implementation patterns
Last updated 27 Mar 2026, 06:51 +0900 .