The current RoseTech API contract.
The API separates safe discovery responses from authenticated write operations. Tokens, API keys, and signing secrets are never included in this public reference.
Explore this surface.
Documentation home
These routes point to live dashboards, real endpoint contracts, and the policies already maintained for RoseTech services.
API reference
The API separates safe discovery responses from authenticated write operations. Tokens, API keys, and signing secrets are never included in this public reference.
Bot operations
Operational controls stay behind authentication, while health and policy information remain available through their public dashboards.
Service policies
Choose a project to open the exact privacy policy or terms of service already maintained for it. This directory does not link to bot-only operational interfaces.
Platform policies
Use these documents for RoseTech-wide privacy and terms. Bot-specific documents remain in the service policy directory.
Uptime discovery
GET /uptime returns the service name, supported heartbeat method, bot identifier sources, and configured bot keys. HEAD returns 204.
Heartbeat ingestion
POST /uptime accepts bot, timestamp or ts, shard, database state, guild count, and additional status fields. Authenticate with X-Uptime-Token or a Bearer token.
Ticket transcript intake
POST /tickets requires X-RoseTech-Api-Key and JSON fields for token, guild, ticket, thread, opener, category, timestamps, closer, plain text, and HTML. A successful response returns the public transcript URL.
Response behavior
JSON errors use the appropriate HTTP status: 400 for invalid payloads, 401 for failed authentication, 404 for unknown bot identifiers, and 405 for unsupported methods.
Highlights
- Send application/json for write endpoints.
- Use Unix seconds for timestamps; heartbeat ingestion also normalizes millisecond timestamps.
- Treat returned transcript tokens as public-view identifiers and never as API credentials.