You're a partner. Register your own end-users with these endpoints, authenticated the same way as any other request from this account — the snc_session cookie set when you log in. No separate API key.
Step 1: log in (get a session cookie)
Calling from a browser that's already logged in here, you can skip this — the cookie is already set. Calling from a script or a server, log in first and save the cookie to a file:
POST https://navlink.net/api/account/login
curl -c cookies.txt -X POST https://navlink.net/api/account/login \
-H "Content-Type: application/json" \
-d '{"email": "you@example.com", "password": "your-password"}'
This writes the cookie into cookies.txt. Every call below reuses it with curl's -b cookies.txt instead of pasting the cookie by hand. It's valid for 7 days — after that, just run this again.
Step 2: register one user
POST https://navlink.net/my/api/bobcat/users
curl -b cookies.txt -X POST https://navlink.net/my/api/bobcat/users \
-H "Content-Type: application/json" \
-d '{"external_id": "your-own-user-id-123"}'
# -> {"uuid": "9a5caf12-...", "external_id": "your-own-user-id-123"}
external_id is optional and is yours to define -- your own user/account id, so you can look a user back up later. Re-posting the same external_id returns the existing row instead of creating a duplicate, so it's safe to retry.
Register many users at once
POST https://navlink.net/my/api/bobcat/users/bulk
curl -b cookies.txt -X POST https://navlink.net/my/api/bobcat/users/bulk \
-H "Content-Type: application/json" \
-d '[{"external_id":"user-1"},{"external_id":"user-2"},{"external_id":"user-3"}]'
# -> [
# {"uuid":"...","external_id":"user-1"},
# {"uuid":"...","external_id":"user-2"},
# {"error":"...","external_id":"user-3"}
# ]
Up to 5000 rows per call. Every row gets its own result -- one bad row doesn't fail the rest of the batch.
List your users
GET https://navlink.net/my/api/bobcat/users
curl -b cookies.txt https://navlink.net/my/api/bobcat/users
What the UUID is for
Each returned uuid is a standard VLESS user id -- hand it to your own end-user to build their own VLESS link, same shape as the VLESS tab's own links (see that tab for a working example you can copy the host/port/service-name/path from).