1barn

Paperwork with an expiry date — Coggins, registration, passport, insurance, memberships — and how close each is to lapsing, the latest expiry first: `limit` papers (20 unless asked, at most 100) from `offset`; a full page means there may be older ones. The number on each paper (`reference`) is shown to staff. `notes` are Markdown; an owner sees only the notes staff shared with them.

barn_horse_renewals

The questions a service day asks about one horse, worded for it, with what the horse's record already says for the linked ones (`prefill`: value and where it came from) and the answers so far. For staff, whose profile the owner questions (phone, contact) read and update: `owner` by name, the horse's `owners`, and with several owners and none picked `owner_pick_needed` (pass `owner_person_id`, one of `owners`, to pick; until then no owner question is filled in). Staff for any horse; an owner for their own.

barn_service_day_form

One person: relationships, login role and status, invite status, vendor_types, organization and labels, with their email, phone, other emails and phones, and mailing and billing addresses when on file. A birth date shows only as date_of_birth_on_file and insurance only as insurance_on_file (true or false); a person reads their own insurance with barn_my_insurance. Staff only.

barn_get_person

A person's and their family's events, past and upcoming, as the person page's Events tab shows them. The family is explicit links only (their children, people who bill to them, anyone on a sign-up they paid for; never matched by email). One item per sign-up: the event and its dates, who paid, source "acuity" for imported history, and each person's status, attendance, add-ons and payment. Payment amounts, credits and refunds only with the finance permission; otherwise payment is {state: paid | balance_due}. Read only. Staff only.

events_person_history

A person's family and emergency links, as their Family card shows them: each link's id, the other person's name and id, what they are (`relation`, read from this person: "parent", "child", "spouse"), and portal sharing: `sharing` none | one_way | both, with `sees` saying exactly who sees whose ("Bo sees Ivy's portal; Ivy doesn't see Bo's"). Staff only.

barn_person_family

What a place is given: its own care lines (place care), such as a paddock's evening bale of hay or a field's trough, which belong to the place and not to any of its horses. Its horses' own care is theirs (barn_horse_care). Find the place with barn_list_spaces. Staff only.

barn_place_care

A service day's questions for owners: the form it follows (if any), whether the day has its own copy, and the form's questions to compare. Staff only.

barn_service_day_questions

A sign-up's money history, one dated line per change ("Oct 19 · Canceled Liam’s spot · $390.00 off the Jun 1 charge (deposit kept)"), each with who did it, what it paid and the totals after it, and Coming up (the next charge). `copy_text` is the lines in plain words for a message. Read only. Owners and managers with the finance permission.

events_signup_history

A template's linked records: the people and horses it is about (`slots`: key, label, person|horse, the participant a person slot is bound to), the relationships between them, and which field is which of their attributes (field_id, label, kind, link_slot, link_attribute). `linked: false` means nothing is saved yet and the slots shown are the defaults (signers bound). Also returns the catalog of attributes, relationship kinds and presets. Staff only.

esign_get_template_links

The horses a vet, farrier or other vendor is linked to here, most urgent first. Each has what's due that this vendor would come out for (a vet: vaccinations, dental, Coggins, health certificates; a farrier: shoeing; `status` overdue, due_soon, or never for something every horse should have and this one has never had on file), whether it's under treatment (injured, rehabbing or sick, with the note), its owner, its home and when this vendor last saw it. `needs` is due or under treatment; `needs_only` keeps just those. `counts` has needs, due, treatment and all. To book one visit for all of them, use barn_create_service_day with `horse_ids`. Staff only.

barn_vendor_horses

The health records a vet, farrier or other vendor is named on as the provider, newest first: the horse, what was done (kind, product, summary) and when. `total` counts them all; page with `offset` and `limit`. Staff only.

barn_vendor_visits

A lesson-linked bookable event's week (week: any YYYY-MM-DD in it): each slot time with who leads it, the starts it offers, the starts held back because its person teaches then (and why), its warnings ("Outside Ella's hours", "No Lead Line horse is free 10:00 AM–11:00 AM") and lessons booked from it; with Who leads' lessons and availability that week. Staff only.

events_slots_week

Add a slot families can book from: one date (on_date) or weekly (weekdays 0=Monday…6=Sunday, from_date, until_date), start_time and end_time "HH:MM". A lesson-linked event's slot names who leads it (provider_person_id, one of the lesson type's Instructors) and its arena, and leads one lesson at a time; the person named is notified. Owners and managers with the calendar permission. Call first without confirm: nothing changes, and the answer says what would; call again with confirm=true only after the person says yes.

events_create_slot

File what a family asked for, for a term: the student, discipline, individual|group, length, lessons per week, preferred instructors (first choice first), and `options` — the windows they can make, ranked: [{weekday: 0=Monday…6, start_time: "HH:MM", end_time: "HH:MM"}]. Returns the request as lessons_requests shows it. Staff only; families ask staff for now.

lessons_create_request

Create a horse (sex: mare|gelding|stallion|unknown). `name` is what the barn calls it; `registered_name`, optional, is what's on its papers. `foaled_on` is the full foaling date (YYYY-MM-DD) when known, and sets the foal year; `weight_lb` is whole pounds; `uses` is any of boarder, competition, pleasure, for_sale, trail, in_training; `height` is hands and inches to the half inch, as said: "15.2", "15.2½", "15h 2.5in", or inches, "62.5in". Staff only.

barn_create_horse

Add a lesson type ("Lead Line, 45 minutes, ages 3 to 8, led by Ella or Kayla on Biscuit or Pepper"). teacher_title: instructor or leader; workload_weight: 1, or 0.5 for light work; max_riders: "Up to N riders" (1 to 20; none is one rider; above 1 the calendar shows its lessons' seats, "2 of 3"). lesson_price_cents: what one lesson costs a rider paying per lesson (a lesson of this type starts at it). Teachers must be marked Teaches or leads lessons. bookable=true also makes its bookable event (a draft families can't see until it's published, with no slots yet). Staff only.

lessons_create_type

Add a make-up credit by hand for one student (one from outside 1barn, or owed for another reason): note is required (staff and the family see it), expires_on defaults to the barn's setting from today, lesson_type_id is optional (it prices a later conversion). Say whose and ask first. Finance.

lessons_add_makeup

Add a note (subject: horse|person; visibility: staff|owners|all, default staff). `body` is Markdown (bold, lists, links), up to 10,000 characters. Docs: https://help.1barn.com/assistants/

barn_add_note

Create a person (a clinic or company itself is barn_create_organization). Boarder, rider and parent are worked out from horses, lessons and family, so aren't set here. A birth date and insurance are entered in the 1barn app, never through an assistant. Returns their id, name, relationships and vendor types. Staff only.

barn_create_person

Write down that something happened (shots given, feet done, the vet out) for one horse or several in one save: the vet did spring shots for the whole barn, the farrier did eight. One record per horse. All or nothing: an unknown or archived horse saves none of them. Staff only.

barn_add_health_records

Add a Ready to add card to 1barn: create the new people and horses, fill the blanks, write the differences chosen, add the relationships and link the signed document to everyone it names. Before calling, read the card (esign_filing) to the person: its questions, its differences and every `confirm` line (overwrites, billing changes, portal sharing), and add only on their yes. `decisions` (optional, saved first): {"slots": {key: {"match": id | "new" | "skip", "items": {attribute: fill | skip | keep | use | add}}}, "relations": {key: {"ticked": bool, "billing": keep | use}}}. Adding twice changes nothing; a card whose matches changed since is refused with the fresh card to read again. Staff only.

esign_file

Add a space to the facility: "Turnout 6", "Stall 12", "Back Pasture". `kind` is a space kind's name or key (see barn_list_space_kinds — stall, turnout, paddock, pasture, barn…). `parent_space_id` puts it inside another space, a stall inside a barn; `capacity` is how many horses it holds, defaulting to the kind's usual number. Staff only.

barn_create_space

Add a kind of space to the barn (Settings › Spaces): "Run-in shed", "Round pen". can_be_home: horses can live in one; can_be_turnout: horses can go out in one; assignable: it takes horses at all (false for a tack room or wash rack); default_capacity: how many horses one usually holds. Spaces of it are then made with barn_create_space. Notifies nobody. The owner, or a manager with the settings permission.

barn_create_space_kind

Add a day someone forgot to clock: the person (staff or an instructor), the work type, the clock-in and clock-out (ISO with the barn's offset), its breaks [{started_at, ended_at}] (unpaid; the entry pays them added up) and a note the employee sees. It's flagged as added by hand and waits for approval under the barn's policy. Propose it with the person, the day, the times, the breaks and the hours. Managers only; refused in a closed pay period. Returns the entry.

staffing_add_entry

Add a kind of vendor to the barn's list (Settings › Vendor types): "Saddle fitter", "Massage". It goes at the end; reorder with barn_reorder_vendor_types. Notifies nobody. The owner, or a manager with the settings permission.

barn_create_vendor_type

Add a section of `type` (text, price, gallery, quotes or events, the Booking section, as many as you like; one each of boarding, lessons, forms and contact) to the draft, after section `after` (default: before Contact), optionally with its `fields` (a booking section: shows, categories, types, event_id, show_photos, as in website_update_section; it starts showing everything). A text, price or booking section gets its own page. `added` is the new section's id.

website_add_section

Add a kind of work to the schedule (barn chores, office, night check…). color: #rrggbb for the schedule, picked for it when left out. hourly_cents: its suggested rate, filled in when someone is assigned it (needs the pay permission; $0 without). Notifies nobody. The owner, or a manager with the settings permission.

staffing_create_work_type

Add one approved sender (owner or manager only): a person in 1barn, an email address, or a whole domain (anyone there; broader). From then on, mail they send to the barn's records address is sent to Anthropic to be read by AI. Before calling, tell the person plainly that mail from this sender will be read by AI (Anthropic) and ask them to confirm; call only after they say yes.

records_add_sender

Add an arena: "Indoor Arena", "Dressage Ring", "Jump Field". `cover` is indoor, covered or outdoor; `size` and `surface` are free text as the barn says them ("60 × 120 ft", "sand and fiber"); `lights` says whether it's lit; `uses` is any of lessons, events, open_riding, lunging, jumping, turnout; `capacity` is how many lessons may run in it at once (the arena kind's usual number when left out); `parent_space_id` puts it inside a barn (an indoor arena under the barn's roof). Anything not said can be added later with barn_update_arena. Staff only.

barn_create_arena

Add a suggestion from the records inbox to 1barn (staff): makes a health record (vaccination, vet_visit, farrier), a Coggins renewal, or documents on the horse (invoice, other), one per horse, with the email's files attached. Give kind, horse_ids, provider_person_id or fields (by name, as records_inbox_item shows them) only to correct the suggestion; anything left out is added as suggested. Check the low_confidence fields with the person first.

records_file

Add a fixed-date event as a draft (publish it in the app or with events_update). With event_type_id it follows that type's four sections (details, price, questions, policies); a field of a followed section given another value is refused unless customize names it. Without event_type_id it's something new and other_dates is required: ask the person, never assume. Nothing converts by itself later (add a day with events_update sessions, or events_convert_to_type). Charges and sends nothing. Staff only.

events_create

Add an event add-on: a name and price in cents (0 is fine), an optional Markdown description, an optional duration in minutes, how many one registration may take (1 = a checkbox), an optional total per event ("8 stalls"), and who offers it: event_type_ids (every event of those types; one can hide it with events_set_event_addons) and event_ids (those events directly). kind="time_based" (spec 46: before/after care, aligned to an event's sessions): price_cents is the all-sessions price, plus price_per_session_cents, price_sessions (how many sessions that price is for), event_limit as spots per session, times [{label, starts_time "07:30", ends_time "09:00"}], offered through event_type_ids (each event follows; set its own with events_set_event_addons). Its booking rules follow the barn's until set with events_update_addon. Charges nobody. Staff only.

events_create_addon

Add an event category (Settings › Events): "Camps". color (#rrggbb): its events' color on the booking calendar; left out, it gets the first color of the barn's brand-aligned palette no other category wears, and keeps it (adding or reordering categories never recolors one). A color too light to show 3:1 on white is refused. Event types are put in one with events_update_type. Notifies nobody. Staff only.

events_create_category

Add an event type: what its events share (price, payment terms, place, "Before you come" text, tips, late sign-ups, reminders). Its events follow it unless one sets its own. Charges nobody. Staff only.

events_create_type

Add an organization: a vet clinic, a farrier's business, a feed company, or the barn's own business ("Stagecoach Stables") that owns horses. It's kept with the barn's people, so it can be a horse's vet or owner, a service day's vendor or the emergency card's vet, just as a person can. It has one `name`, its own `email` (the front desk), `phone`, `website`, `address` ({street1, street2, city, state, postal_code, country}) and `vendor_types` (the barn's names or keys, barn_list_vendor_types: a clinic is "Vet"). It can't sign in or be billed, and has no birth date or rider level. Add the people who work there with barn_create_person's `organization`, or barn_update_person's for someone already in the barn. Returns its id, name and vendor types. Staff only.

barn_create_organization

Give someone an interest in a horse from a date; this is also what lets them see the horse at all (a full lease is usually a lessee row). It adds a party without ending anyone else's: use barn_transfer_horse for a sale. No money: leases are billed elsewhere. Returns the party with its summary ("Half lease · rides Tue, Thu, Sat"). Staff only.

barn_add_party

Add days to the barn's holiday calendar, all or nothing. Each: {date: ISO date, name, multiplier?: times the rate, 1 to 9; left out it stores the barn's holiday rate as the holiday's own, paid?: a paid holiday, true when left out, paid_on?: ISO date it's paid on; left out it stores the barn's weekend rule's day as its own}. Up to 40. Two paid holidays can't share a paid day. A day already on the calendar is skipped and listed under skipped; a day in a closed pay period refuses the lot (reopen it first). Hours worked on a holiday pay more in every open pay period that holds it, so say which days and at what rate and confirm with the person before calling. Notifies nobody. Needs the settings permission.

staffing_add_holidays

Put horses on a service day, each its own way: [{horse_id, mode: ask | fill | none, answers?, finished?}]. `ask` sends the owner a notice and an email to answer in 1barn; `fill` saves `answers` now (keyed by question id, short name or label); `none` puts the horse on with nothing asked. All or nothing when it can't be done (not your horse, closed, full); a horse already on is skipped. When any horse is `ask`, call it first without confirm: nothing is added, and the answer says who would hear; call again with confirm=true only after the person says yes. Modes are staff's; an owner's entries are their own horse's answers.

barn_add_horses_with_answers

Ask more people (on the staff list) in a request round that's still open. They're notified. Before confirming, say who and ask. Managers.

staffing_add_to_round

A manager adds approved time off for an employee who didn't ask ("put Maya down for Friday off, from her vacation"). Refused for past days and when they already have time off then. Call it first without confirm: nothing is saved, and the answer says what would be added, the hours, the balance after, any days_without_hours (ask how many hours each pays, never guess) and lessons it touches with their choices; call again with confirm=true only after the person says yes. Confirmed, it takes paid hours from the balance, closes their bookable slots on whole days off and notifies the employee. Returns the time off and the shifts it covers. The reason is seen only by managers and the employee. Managers only.

staffing_add_time_off