Aura++ · Partner API · v1
Partner Premium Submit API
Official documentation for submitting and scheduling Premium launches on Aura++ from external products, directories, and partner platforms. Projects are created under the license-linked Aura++ account and follow the same Premium rules as Bulk / Premium Launcher in the dashboard.
On this page
Overview
The Partner Premium Submit API lets authorized partners create Premium launch listings programmatically. Typical use cases include directory submission forms, agency launch tools, and multi-product launch workflows.
- Base URL:
https://auraplusplus.com/api/partner/v1 - Protocol: HTTPS · JSON request and response bodies
- Launch type: Premium only (not Premium Plus)
- Billing: Covered by the linked Premium Launcher license — no per-submit Stripe checkout
- Machine-readable spec: /openapi.json
Ownership: each successful submit creates a project under the Aura++ account linked to the license key. Confirmation is sent to the partner account and to customerEmail.
Authentication
All endpoints require a Premium Launcher license key as a Bearer token.
Authorization: Bearer YOUR_LICENSE_KEY- Sign in to the Aura++ account that should own partner-submitted launches.
- Open Dashboard → Bulk and link a valid Premium Launcher license key.
- Store the key server-side only. Do not expose it in client-side JavaScript or public repositories.
Missing, unlinked, invalid, or expired keys return 401 with a structured error payload.
Limits & rules
Partner submits follow the same Premium scheduling rules as the dashboard:
- One launch per calendar day per Aura++ account
- Shared global Premium capacity (limited slots per day across the platform)
- Bookable window: 1–60 days ahead · launches at 08:00 UTC
- Premium launches only
- Logo and product images must be hosted by the partner and provided as HTTPS URLs (no upload endpoint)
- Description minimum: 200 words
- Categories: 1–3 IDs from
GET /categories - Tech stack: 1–5 items
Need a second daily slot? Use a separate Aura++ account with its own linked Premium Launcher license. Accounts are independent.
Endpoints
GET /categories
Returns category id / name pairs for form mapping. Cacheable; refresh periodically.
GET https://auraplusplus.com/api/partner/v1/categories
Authorization: Bearer YOUR_LICENSE_KEY{
"categories": [
{ "id": "…", "name": "…" }
]
}GET /availability
Returns Premium dates the authenticated account can still book (global slots remaining and the account has not already used its one launch that day).
GET https://auraplusplus.com/api/partner/v1/availability
Authorization: Bearer YOUR_LICENSE_KEY
Optional query:
?from=YYYY-MM-DD&to=YYYY-MM-DDfrom / to are optional and clamped to the Premium scheduling window.
{
"launchType": "premium",
"dates": [
{
"date": "2026-09-15",
"available": true,
"premiumSlotsRemaining": 7
}
]
}POST /projects
Creates the project under the license-linked account and schedules a Premium launch for the requested date.
POST https://auraplusplus.com/api/partner/v1/projects
Authorization: Bearer YOUR_LICENSE_KEY
Content-Type: application/json
{
"customerEmail": "customer@example.com",
"name": "Example Product",
"websiteUrl": "https://example.com",
"description": "(≥ 200 words)",
"logoUrl": "https://cdn.example.com/logo.png",
"productImageUrl": "https://cdn.example.com/product.png",
"categories": ["<category-id>"],
"techStack": ["Next.js", "TypeScript"],
"platforms": ["web"],
"pricing": "freemium",
"pricingDetails": "Free + Pro from $29/mo",
"makerName": "Jane Doe",
"launchDate": "2026-09-15"
}| Field | Required | Notes |
|---|---|---|
| customerEmail | Yes | Receives launch confirmation |
| name | Yes | Max 120 characters |
| websiteUrl | Yes | Must be unique on Aura++ |
| description | Yes | ≥ 200 words |
| logoUrl | Yes | HTTPS |
| productImageUrl | Yes | HTTPS |
| categories | Yes | 1–3 IDs from GET /categories |
| techStack | Yes | 1–5 strings |
| platforms | Yes | web, mobile, desktop, api, other |
| pricing | Yes | free, freemium, or paid |
| pricingDetails | Conditional | Required when pricing is freemium or paid |
| makerName | Yes | Max 120 characters |
| launchDate | Yes | YYYY-MM-DD from availability |
| githubUrl | No | Optional |
| twitterUrl | No | Optional |
Success response:
{
"ok": true,
"projectId": "…",
"slug": "…",
"launchDate": "2026-09-15",
"projectUrl": "https://auraplusplus.com/projects/…"
}Errors
Failed requests return JSON with error (human-readable) and code (machine-readable).
{
"error": "…",
"code": "validation_error"
}| HTTP | Example codes | Meaning |
|---|---|---|
| 401 | missing_auth, invalid_license | License missing, not linked, invalid, or expired |
| 400 | invalid_json, validation_error, invalid_categories, invalid_range | Malformed request or field validation failure |
| 409 | url_exists, date_full, daily_limit | Website URL already listed, date unavailable, or daily account limit reached |
| 500 | server_error | Unexpected server failure — retry with backoff |
Integration checklist
- Link a Premium Launcher license in Dashboard → Bulk.
- Call
GET /categorieswhen building the submission UI (cache the response). - Call
GET /availabilitywhen the user opens the date picker. - On submit, call
POST /projectsfrom your backend with the license key. - Surface
projectUrlto the customer on success. - Refresh availability after a successful booking.