Every Nudj API endpoint is scoped to your organisation’s domain. This page explains the patterns in use and points you at the Admin API endpoints that manage white-label custom domains.Documentation Index
Fetch the complete documentation index at: https://docs.nudj.cx/llms.txt
Use this file to discover all available pages before exploring further.
Looking to add a white-label domain for your members? The full admin walkthrough lives at Custom Domain Setup.
Domain patterns
Your organisation’s API endpoints follow this pattern:| Pattern | Example | When used |
|---|---|---|
| Standard Nudj subdomain | acme-corp.nudj.cx | Default for every organisation |
| Custom subdomain | api.yourcompany.com | Registered via POST /domains |
| White-label | rewards.enterprise.com | Registered via POST /domains, often paired with a member-facing brand domain |
acme-corp.nudj.cx cannot be replayed against a different organisation’s subdomain. This is enforced by the auth middleware at request time.
Managing custom domains via the Admin API
The Admin API exposes three endpoints for custom-domain lifecycle:GET /domains
List every domain registered for your organisation.
POST /domains
Register a new custom domain. Triggers DNS + SSL provisioning.
POST /domains/remove
Retire a domain. Existing tokens scoped to that domain stop being accepted.
Using your domain from code
When building an integration, always use your organisation’s actual domain — never a hard-coded dev/staging host.Finding your domain
- Check Developer Settings — Settings → Organisation → Developer lists the active domain for your organisation.
- Match your admin URL — the admin dashboard for your organisation runs on the same subdomain (e.g. admin is served under
{your-subdomain}.nudj.cx). - Ask your administrator — they have the full list of registered custom domains and can issue a new one via the Admin API or the admin UI.
Troubleshooting
404 Not Found
404 Not Found
- Verify you’re hitting your organisation’s actual domain — not
nudjdevornudjstaging. - Check the path starts with
/api/v2/and usesintegration,admin, oranalytics. - Confirm the endpoint exists for the API type you’re calling.
401 Unauthorized
401 Unauthorized
CORS errors
CORS errors
- The APIs are not CORS-enabled for browser origins. Proxy all requests through your own backend — do not call these endpoints directly from a browser.
Related
Testing Guide
Using the interactive playground and transforming generated cURL snippets for your domain.
Custom Domain Setup (Admin)
Full DNS and SSL walkthrough for registering a white-label domain.

