# Videographer.org

The second-shooter network. Videographers mark the dates they are free, and other
videographers who are already booked find them for those dates. Nobody here is a
client: every account on this property is a videographer, and the thing being
exchanged is one shift of crew work.

## What an agent can do here
POST https://videographer.org/api/account/availability — Mark your own days available or busy
GET https://videographer.org/api/second-shooter — Search the network for an available peer
POST https://videographer.org/api/second-shooter/request — Ask a peer to shoot a date with you
POST https://videographer.org/api/second-shooter/request/{id}/{action} — Accept or decline an inbound request
GET https://videographer.org/api/account/connections — Your crew requests, both directions
GET https://videographer.org/api/read — Read a described gig into the fields a crew search takes
POST https://videographer.org/api/event — Record a page view

The full contract is https://videographer.org/openapi.json (OpenAPI 3.1). 5 of those
7 operations are videographer.com's crew router, mounted here — the
same code answers them on both properties, so a client written against either
works against both.

## Two things to know before you build against this
1. DELIVERY DEPENDS ON THIS DEPLOYMENT. Asking a peer always writes the
   request and queues a heads-up email with status `queued`; whether that mail leaves
   depends on whether the operator has armed a sender, so do not build on the mail
   arriving. Signing in is the reliable path: the person you asked sees the request in
   their requests list either way. AS DEPLOYED RIGHT NOW: a sender is wired and NOT armed, so nothing leaves the building yet.
2. THE API TAKES A SESSION COOKIE, NOT A TOKEN. The 5 crew operations
   authenticate from a cookie minted at https://videographer.com. That property also serves
   /api/account/agent-credential, which mints scoped tokens these routes do not
   accept — so an unattended agent cannot currently hold crew credentials.

## Two paths that are this property's own
GET /api/read reads a described gig — "a 6-hour wedding in Austin, two cameras" —
into the fields a crew search takes, using the same parser videographer.com prices
client work with. It turns words into a search and promises nothing about who is
free.

POST /api/event records a page view and nothing else. It never carries a name, an
id or an email.

## Being found here is opt-in and off by default
A videographer is discoverable only after switching it on, separately from marking
any date. A search that returns nobody is a real answer about this network, not an
error and not a filter to widen.

## Elsewhere in this network
- https://videographer.com/docs — rendered docs for the crew contract these two properties share
- https://videographer.com/llms.txt — Describe a shoot, get a budget, get matched.
- https://videographer.net/llms.txt — The directory — browse videographers by city and shoot type.