HTTP API Reference
Full REST API for chat, threads, and streaming. Build custom integrations with standard HTTP endpoints and predictable contracts.
What this solves
AI chat REST API reference
HTTP API for conversational AI
Chat API documentation
Streaming AI API endpoints
Frequently Asked Questions
HTTP API Reference
What endpoints does the Interlocute API expose?
Each node exposes a /chat endpoint for sending messages, thread management endpoints for listing and continuing conversations, and streaming endpoints for real-time token delivery via SSE. All endpoints follow standard REST conventions with JSON request and response bodies.
Do I need an SDK to use the API?
No. The API uses standard HTTP with JSON payloads. Any HTTP client in any language works. SDKs are optional conveniences, not requirements.
How does streaming work over the API?
Set the Accept header to text/event-stream to receive server-sent events. Each event contains a token or metadata chunk. The stream closes when the response is complete. This gives your UI real-time character-by-character delivery.
Are request and response shapes stable?
Yes. The API follows a versioned contract. Request and response shapes for v1 are stable and will not change in breaking ways. New optional fields may be added without breaking existing clients.
How is authentication handled?
Include your API key in the Authorization header as a Bearer token. Publishable keys are used for client-side embeds (scoped by domain allowlist). Secret keys are used for server-side integrations. Both key types support rotation and usage limits.
Ready to build?
Deploy your node in seconds and start using HTTP API Reference today.