Streaming APIs in Nordcraft allow you to deliver data to users incrementally as it becomes available, reducing wait times and improving the user experience. Instead of waiting for a complete response, users see information as it arrives.

This feature is particularly valuable when integrating AI chatbots or other systems that generate content progressively, letting users see responses as they're being created rather than waiting for the entire content to be generated.

Nordcraft supports two streaming formats:

• Server-sent events (SSE)
• JSON streaming

Server-sent events (SSE) use the text/event-stream content type to establish a one-way connection where the server sends a stream of events to the client.

Each event consists of up to four fields:

• id: The event identifier
• event: The event type
• data: The event payload
• retry: Time in milliseconds before reconnection attempts

When Nordcraft receives a complete event, it triggers an On message event with the event data. This is provided as a CustomEvent where the detail property contains the event fields (see above).

JSON streaming uses the application/stream+json or application/x-ndjson content type to deliver a sequence of complete JSON objects.

When Nordcraft receives a complete JSON object, it triggers an On message event with the parsed object as the event data. This is provided as a CustomEvent where the detail property contains the JSON object.

Process streamed data

To process streamed data in your application:

1. 1

   Navigate to the Events tab in your API configuration
2. 2

   Add an On message event handler that processes each incoming message
3. 3

   Access the message data through the event object

The structure of the data depends on the streaming type:

• For server-sent events, the event detail contains the event fields ( id, event, data, retry)
• For JSON streaming, the event detail contains the parsed JSON object

Nordcraft automatically determines how to parse streamed responses based on the Content-Type header:

• text/event-stream is parsed as server-sent events
• application/stream+json or application/x-ndjson is parsed as JSON streaming

Parse response

If your backend service doesn't set the correct header, you can override the default behavior:

1. 1

   Go to the Advanced tab in your API configuration
2. 2

   Find the Response parsing section and select the appropriate option:
   • Event stream for server-sent events
   • JSON stream for JSON streaming

This forces Nordcraft to parse the response using your specified format regardless of the Content-Type header.

A common application for streaming is with AI-powered chatbots:
User types a question → API request → AI service starts generating a response → Response streams back in chunks → Each chunk appears in the UI as it arrives

This approach creates a more interactive experience where users don't have to wait for the complete response before seeing any output.

When working with streaming APIs:

• Use streaming for long-running operations where progressive updates improve user experience
• Handle partial or incomplete data appropriately in your UI
• Consider fallback behavior for users with unstable connections
• Implement appropriate error handling for interrupted streams