Subscription Server
A separate HTTP/HTTPS server that serves proxy subscription links (standard, JSON, and Clash) to clients. The server listens on its own port (default 2096) and is configured in Settings → Subscription. Fresh panels generate random path prefixes for each format; all paths remain configurable. Every subscription endpoint sets response headers for client apps to read traffic/expiry info.
API token from Settings → Security → API Token. Send as Authorization: Bearer <token>.
In: header
Path Parameters
Client subscription ID.
Query Parameters
Set to "info" to get the subscription status view-model as JSON instead of the links.
Response Body
application/json
curl -X GET "https://example.com/stringstring"{ "success": true, "msg": "string", "obj": null}API token from Settings → Security → API Token. Send as Authorization: Bearer <token>.
In: header
Path Parameters
Client subscription ID.
Response Body
curl -X HEAD "https://example.com/stringstring"API token from Settings → Security → API Token. Send as Authorization: Bearer <token>.
In: header
Path Parameters
Client subscription ID.
Response Body
application/json
curl -X GET "https://example.com/stringstring"{ "success": true, "msg": "string", "obj": null}API token from Settings → Security → API Token. Send as Authorization: Bearer <token>.
In: header
Path Parameters
Client subscription ID.
Response Body
curl -X HEAD "https://example.com/stringstring"API token from Settings → Security → API Token. Send as Authorization: Bearer <token>.
In: header
Path Parameters
Client subscription ID.
Response Body
application/json
curl -X GET "https://example.com/stringstring"{ "success": true, "msg": "string", "obj": null}API token from Settings → Security → API Token. Send as Authorization: Bearer <token>.
In: header
Path Parameters
Client subscription ID.
Response Body
curl -X HEAD "https://example.com/stringstring"
3x-ui