List the client's ads connection sessions

GET /api/embed/ads-sessions

Most recent first (up to 200). It never mixes with the channel signup sessions: each flow has its own surface. Requires the marketing:read scope.

Authentication

Send your API key in the x-neike-api-key header. Console sessions can use a bearer JWT plus x-neike-client-id instead.

Responses

Status	Description	Schema
200	—	—

Example

curl -X GET https://api.neike.dev/api/embed/ads-sessions \
  -H "x-neike-api-key: whk_live_…"