Caching with ETags

Single-resource endpoints set an ETag header. Send If-None-Match on subsequent requests to short-circuit unchanged responses with 304 Not Modified.

Example

First request:

GET /organizations/3/collabs/9.json
Authorization: Bearer <token>
Accept: application/json

HTTP/1.1 200 OK
ETag: W/"5f3a9c1e..."
Content-Type: application/json

{ "id": 9, "name": "Spring lipsticks", ... }

Second request, supplying the previous ETag:

GET /organizations/3/collabs/9.json
Authorization: Bearer <token>
Accept: application/json
If-None-Match: W/"5f3a9c1e..."

HTTP/1.1 304 Not Modified

No body is returned. The agent should treat its cached representation as still current.

When to use it

• Long-polling or periodic refresh of a single resource (e.g. a collab a user is editing)
• Reducing bandwidth on mobile / agent contexts
• Avoiding LLM context bloat when re-fetching unchanged data

Collection endpoints (index) do not currently set ETags — only show.