API
API Overview
Use Qorlivo's public REST API to create links, manage videos and domains, read analytics, and automate workflows.
The Qorlivo public API lets your own tools create and manage Qorlivo resources. Use it for campaign automation, company dashboards, CMS workflows, reporting, and link generation from other products.
Base URL
https://www.qorlivo.com/api/v1
All examples in this section use relative paths such as /links. Prefix them with the base URL when sending requests.
Authentication
Every API request requires a secret API key.
Authorization: Bearer qrlv_live_your_api_key
Create and revoke API keys from Settings, then Developers in the Qorlivo dashboard. See Authentication for key handling and plan access.
Resources
| Resource | Methods | Purpose |
|---|---|---|
/ | GET | Return the API discovery manifest. |
/links | GET, POST | List or create short links. |
/links/{id} | GET, PATCH, DELETE | Read, update, or delete one link. |
/links/bulk | POST | Create up to 100 links in one request on supported plans. |
/videos | GET, POST | List videos or create a video upload. |
/videos/{id} | GET, PATCH, DELETE | Read, update, or delete one video. |
/domains | GET, POST | List or add custom domains. |
/domains/{id} | GET, DELETE | Read or remove one domain. |
/analytics | GET | Read click and visitor analytics. |
Discovery
Use the API root to inspect the current public resources.
curl https://www.qorlivo.com/api/v1 \
-H "Authorization: Bearer $QORLIVO_API_KEY"
Example response:
{
"version": "v1",
"baseUrl": "https://www.qorlivo.com/api/v1",
"resources": {
"links": {
"methods": ["GET", "POST"],
"href": "https://www.qorlivo.com/api/v1/links"
}
}
}
Plan access
| Capability | Availability |
|---|---|
| Read existing resources | All plans with an API key. |
| Create, update, or delete resources | Creator and higher. |
| Bulk link creation | Business and Enterprise. |
| Webhooks | Pro and higher. |
If a plan does not include an action, the API returns 403 with a message explaining the requirement.
Pagination
List endpoints use a limit query parameter. Links also return cursor fields for paging through larger lists.
GET /api/v1/links?limit=50&cursor=1720000000000
Example paged response:
{
"data": [],
"hasMore": true,
"nextCursor": 1720000000000
}
Use nextCursor from one response as the cursor value on the next request.
Dates
Qorlivo accepts ISO 8601 date strings for link expiration and analytics date filters. Video expiration uses a future timestamp in milliseconds.
{
"expiresAt": "2026-08-01T00:00:00.000Z"
}
Error format
Errors return JSON with an error object.
{
"error": {
"message": "Missing required field: url",
"code": 400
}
}
See Errors & Rate Limits for status codes and retry guidance.
Recommended integration pattern
- Create one API key per app or automation.
- Store the key in a server-side secret manager.
- Begin by calling
GET /api/v1. - Create links with
POST /links. - Store returned IDs for future updates or analytics queries.
- Add webhooks if your app needs to react to link lifecycle events.
- Handle
401,403,409, and429explicitly.