This page needs special handling because it appears in the finalized IA and the endpoint inventory, even though the audit’s numbered page-by-page section stops at Billing.
Endpoints
| Method | Path | Purpose |
| GET | /support/my-session | Resolve or create support chat session |
| GET | /support/existing-session | Find an existing support chat session |
| POST | /feature-interest | Register feature interest |
| GET | /feature-interest/status | Check feature-interest status |
The Support session endpoints use an authenticated workspace user and accept a channelToken query parameter.
Resolve Support Session
GET /support/my-session?channelToken=<SUPPORT_CHANNEL_TOKEN>
Authorization: Bearer <AUTH0_ACCESS_TOKEN>
The response resolves a Visitor Session payload for the YS Desk support conversation.
Existing Support Session
GET /support/existing-session?channelToken=<SUPPORT_CHANNEL_TOKEN>
Authorization: Bearer <AUTH0_ACCESS_TOKEN>
The response contains the existing session or null when one does not exist.
Feature Interest
POST /feature-interest
Authorization: Bearer <AUTH0_ACCESS_TOKEN>
x-workspace-id: <WORKSPACE_ID>
The audited request supports:
{
“featureName”: “<FEATURE_NAME>”,
“message”: “Interested in this feature.”
}
Need Help?
Email: support@ysdesk.com
Documentation: https://docs.ysplugins.com/ys-desk