# Printing a photobook

> Arrange a trip's photobook draft — size, cover, photographs. Ordering and paying stay the owner's own page.

## Arranging a book, not ordering one

```http
PUT /api/v2/{user}/photobooks/drafts/{trip}
Content-Type: application/json
Authorization: Bearer fs_agent_…
```

Writes the trip's own draft arrangement — size, cover, which photographs, per-day layout and the rest of a photobook's own options — the same row the owner's browser reads and writes from their trip's own page. **This charges nothing, builds nothing and prints nothing.** Choosing the book, paying for it and sending it to the printer stays one page and one press, owner-only, outside `/api/v2` entirely — there is deliberately no call here that does any of those three. `GET` at the same address reads the draft back.

Once a book has actually been ordered, this is the one thing you can do:

```http
GET /api/v2/{user}/photobooks/orders/{id}
Authorization: Bearer fs_agent_…
```

Reads its size, cover, cost, and — once it has gone to the printer — who it went to, by `contactId` and never a street address. Say what this call reports; do not say a book has been printed or is on its way because you arranged one, only when this call says so.