# Request format

> Flat JSON field maps on create and update — not JSON:API.

Source: https://streams.dev/docs/api/requests

Create and update endpoints accept **flat JSON** (or form-encoded) field maps. The API does not use JSON:API resource objects or `data.attributes` envelopes for input.

## Create entry

`POST /api/streams/{stream}/entries`

```bash
curl -s -X POST "http://localhost/api/streams/films/entries" \
  -H "Content-Type: application/json" \
  -d '{"title":"Star Wars","director":"George Lucas"}'
```

The `CreateEntry` endpoint passes the JSON body to `newInstance()` on the stream's entries.

## Update entry

**PUT** sets the JSON body on the entry with `setAttributes()`; **PATCH** assigns each field in the body one at a time. Both return **200** when they update and **201** when the entry didn't exist and was created. See [Entry endpoints](/docs/api/entry-endpoints#update-entry).

```bash
curl -s -X PATCH "http://localhost/api/streams/films/entries/1" \
  -H "Content-Type: application/json" \
  -d '{"title":"Updated Title"}'
```

The route `{entry}` id is set on the payload from the URL segment.

## Create/update stream

Same flat JSON shape for stream definition entries on `/api/streams` endpoints.

## Query endpoint (different shape)

`POST /api/streams/{stream}/query` uses a `parameters` array — see [Query endpoint](/docs/api/query-endpoint).

## Related

- [Entry endpoints](/docs/api/entry-endpoints)
- [Responses](/docs/api/responses)
- [Errors](/docs/api/errors)