Event sequence for /v1/messages
/v1/messages with stream: true emits the event sequence below regardless of which upstream provider served the request.
Request#
Set stream: true on /v1/messages.
curl -N https://api.atptoken.ai/v1/messages \
-H "Authorization: Bearer atp-..." \
-H "anthropic-version: 2023-06-01" \
-H "Content-Type: application/json" \
-d '{
"model": "claude-haiku-4-5",
"max_tokens": 256,
"stream": true,
"messages": [{ "role": "user", "content": "Say hi in 3 words" }]
}'Event sequence#
event: message_start
data: {"type":"message_start","message":{...}}
event: content_block_start
data: {"type":"content_block_start","index":0,"content_block":{"type":"text","text":""}}
# one per delta:
event: content_block_delta
data: {"type":"content_block_delta","index":0,"delta":{"type":"text_delta","text":"..."}}
event: content_block_stop
data: {"type":"content_block_stop","index":0}
event: message_delta
data: {"type":"message_delta","delta":{"stop_reason":"end_turn"},"usage":{"output_tokens":N}}
event: message_stop
data: {"type":"message_stop"}ping events can arrive anywhere in the stream (usually right after message_start and after content_block_start). They carry no data — skip them.
Events#
Response#
A complete response from claude-haiku-4-5:
event: message_start
data: {"message":{"id":"01M3F85T5YV4BEGMA014TVTC9E","type":"message","usage":{"input_tokens":32,"cache_read_input_tokens":0,"cache_creation_input_tokens":0,"cache_creation":{"ephemeral_1h_input_tokens":0,"ephemeral_5m_input_tokens":0},"output_tokens":1},"role":"assistant","content":[],"model":"claude-haiku-4-5-20251001","stop_sequence":null,"stop_reason":null},"type":"message_start"}
event: ping
data: {"type":"ping"}
event: content_block_start
data: {"index":0,"type":"content_block_start","content_block":{"type":"text","text":""}}
event: ping
data: {"type":"ping"}
event: content_block_delta
data: {"index":0,"type":"content_block_delta","delta":{"type":"text_delta","text":"Hi there"}}
event: content_block_delta
data: {"index":0,"type":"content_block_delta","delta":{"type":"text_delta","text":" friend!"}}
event: content_block_stop
data: {"index":0,"type":"content_block_stop"}
event: message_delta
data: {"type":"message_delta","usage":{"input_tokens":32,"cache_read_input_tokens":0,"cache_creation_input_tokens":0,"output_tokens":7},"delta":{"stop_sequence":null,"stop_reason":"end_turn"}}
event: message_stop
data: {"type":"message_stop"}Read usage from message_delta#
Always take token counts from message_delta, not message_start. The usage in message_start is not final; message_delta carries the final input_tokens and output_tokens.
Tool use#
When the model calls a tool, the block starts as tool_use with an empty input, and the arguments arrive as JSON fragments in input_json_delta events. Concatenate every partial_json for that index and parse the result once at content_block_stop. The first fragment can be an empty string.
event: ping
data: {"type":"ping"}
event: content_block_start
data: {"index":0,"type":"content_block_start","content_block":{"id":"toolu_01PGo2evEeMN4XS8geMjN7Vs","input":{},"name":"get_weather","type":"tool_use"}}
event: ping
data: {"type":"ping"}
event: content_block_delta
data: {"index":0,"type":"content_block_delta","delta":{"type":"input_json_delta","partial_json":""}}
event: content_block_delta
data: {"index":0,"type":"content_block_delta","delta":{"type":"input_json_delta","partial_json":"{\"city\": "}}
event: content_block_delta
data: {"index":0,"type":"content_block_delta","delta":{"type":"input_json_delta","partial_json":"\"Taipe"}}
event: content_block_delta
data: {"index":0,"type":"content_block_delta","delta":{"type":"input_json_delta","partial_json":"i\"}"}}
event: content_block_stop
data: {"index":0,"type":"content_block_stop"}
event: message_delta
data: {"type":"message_delta","usage":{"input_tokens":672,"cache_read_input_tokens":0,"cache_creation_input_tokens":0,"output_tokens":39},"delta":{"stop_sequence":null,"stop_reason":"tool_use"}}Treat the tool call id (for example toolu_…) as opaque. Send it back unchanged as tool_use_id in your tool_result.
Stop reasons#
stop_reason maps from the provider: stop → end_turn, length → max_tokens.
Errors#
Errors found before streaming starts come back as a normal JSON response with an HTTP status and no event stream. Check the status (or Content-Type: text/event-stream) before you start reading events.
If the connection closes before message_stop, treat the response as incomplete. See Error codes for retry guidance.