API reference
API overview
The Roblox SDK writes telemetry to the configured ingestion origin. The application API handles signed-in workspace requests on prisma.astil.io.
SDK telemetry in staging
Use protocol version 1 and the HTTPS ingestion origin issued for your staging source. The SDK sends JSON and manages enrollment, token renewal, and bounded delivery retries.
| Route | Authentication and response |
|---|---|
POST /sdk/v1/sessions | Server enrollment credential. Success returns 200 with a session ID and a 15-minute ingest token. |
POST /sdk/v1/events | Session ingest token. Success returns 202 after the event batch is acknowledged by Kafka. Archive and query delivery follow independently. |
On a delivery timeout, 429, or 503, the SDK retries with the original event IDs and honors Retry-After when present. See the staging setup for credential instructions.
Application API
Invited users can sign in to a workspace. The following routes use the browser session and return JSON 401 for signed-out requests.
GET /api/v1/mefor the current account and workspace context.GET /api/v1/experiencesfor experiences the signed-in user can access.
Unknown API paths return a JSON 404. The first telemetry integration will add server health reads for a permitted Roblox universe and environment.
GET /api/v1/experiences/{universe_id}/environments/{environment}/serversto browse servers.GET /api/v1/experiences/{universe_id}/environments/{environment}/servers/{server_id}for an instance’s health and reporting freshness.
universe_id is the Roblox universe ID. A place is a filter within that universe. The application API will use a customer session and verify the requested scope on every call.