> ## Documentation Index > Fetch the complete documentation index at: https://docs.rescueconsole.com/llms.txt > Use this file to discover all available pages before exploring further. # Add a record to many animals > Adds the same medical record to up to 100 animals at once, such as a vaccine given at a clinic day. What is the same for every animal goes in record; what is each animal's own (a lot number, a tag number, a test result, a note) goes on that animal's entry and is merged over it. next, when you send it, is the follow-up record and is made on every animal too. All or nothing: every animal's record is checked before any is written. When the record is refused on any animal, nothing is added, and the refusal (400) lists each animal it was refused for in problems, with animal_id, name and error. A record due and not yet done makes a task on each animal, and a spay or neuter procedure that is done updates the animal's altered details. Needs **write** on Animals. ## OpenAPI ````yaml /api-reference/openapi.json post /api/animals/medical/bulk openapi: 3.1.0 info: title: RescueConsole API version: '2026-09-19' description: >- Your own organization's records, from your own software. There is no sandbox: every request goes to your live organization. servers: - url: https://{organization}.rescueconsole.com description: Your own organization's address, the one you sign in at. variables: organization: default: your-rescue description: >- The first part of the address you sign in at. A key only works at the address of the organization it was made in. security: - apiKey: [] tags: - name: Animals description: The animals in your care, and the ones you have placed. - name: Animal notes description: Notes written on an animal's record. - name: Animal weights description: An animal's weight readings, one per weighing. - name: Animal medical records description: >- Vaccines, treatments, procedures, tests, exams and other medical records on one animal. - name: Animal placements description: The people an animal came from or has been placed with, over time. - name: Animal nutrition description: 'What an animal eats: its feeding list and its diet.' - name: Animal relationships description: Siblings, parents, offspring and bonded pairs. - name: Animal tags description: Your own short labels on an animal. - name: Breeds description: The breed or kind lists your intake form offers for each species. - name: Litters description: Litters, and the animals born into them. - name: Locations and housing description: >- The places animals are housed at each of your locations: campuses, buildings, rooms and cages, the tunnels that join cages into one space, and who is in each. - name: Foster homes description: >- The people who foster for you, what each home can take, and the animals offered to and placed with them. - name: Intakes description: >- How each animal arrived: the route in, who brought it, why it was given up and the state it came in. - name: Medical due description: >- Medical work that is outstanding across all your animals, and one medical record added to many animals at once. - name: Transports description: >- Transport runs: a chain of drives, each leg with its own driver, that moves animals from one place to another. - name: Animal calendar description: >- The dated things in animal care on one calendar: medical work due, adoptions, foster placements starting and ending, arrivals, and meet and greets. - name: Animal reports description: >- The operations report: intakes, outcomes, live release rate and the animals in your care, each figure with its own definition. - name: Adoption applications description: >- Applications to adopt or foster, from first draft to a decision, and the adoption contract signed on an approved one. - name: Adoptions description: >- Animals that went home, what each adopter owes and has paid, and closing or reversing the adoption. - name: Signed contracts description: >- Contracts signed on an adoption, a foster placement or an intake, each kept exactly as it read when it was signed. - name: Contract templates description: >- The contracts your organization has people sign, with the merge fields that fill them in. - name: Reconciliations description: >- A payment processor's settlement lines, matched against the adoption payments you recorded. - name: Animal custom fields description: >- The extra fields your organization adds to animals, housing units and adoption applications. - name: Age groups description: >- What counts as a baby, an adult or a senior, per species, which fee rules and discounts read. - name: Animal statuses description: >- Your organization's status vocabulary for animal records, and what kind of status each one is. - name: Application stages description: >- The steps an adoption or foster application moves through before it is decided, in your organization's words. - name: Behaviour attributes description: >- The catalogue of behavioural traits, and where a trait with each name may be shown beyond the record. - name: Cage card templates description: >- The layouts your organization prints for the kennel door: paper, fields, photo and QR code. - name: Adoption fee schedules description: >- The rules that suggest an animal's adoption fee, and the discounts laid over them. - name: Medical catalogue description: >- The diagnoses, tests, vaccines, treatments, procedures, conditions and medications your medical records pick from. - name: People description: >- The people your organization deals with: adopters, donors, volunteers, fosters and everybody else. - name: Person notes description: Notes written on a person's record. - name: Person contacts description: >- A person's phone numbers and email addresses, one of each kind marked primary. - name: Person addresses description: A person's addresses, one of them primary. - name: Person tags description: Free-text labels on a person, added and removed one at a time. - name: People duplicates description: People who look like the same person entered twice, and merging them. - name: People custom fields description: The fields a person's record carries beyond the standard ones. - name: Organizations description: >- The outside organizations your rescue deals with: veterinary practices, partner rescues, shelters, suppliers, employers and agencies. - name: Organization locations description: An organization's places, one of them the main one. - name: Affiliations description: >- Who works at, volunteers for or otherwise belongs to an organization, now or in the past. - name: Forms description: >- The forms your organization publishes, such as an adoption application or a volunteer sign-up, and the questions on them. - name: Submissions description: >- What people sent through your forms, and what your team does with each one. - name: Tasks description: >- To-dos, on a record or for the whole organization, narrowed to the records your key may read. - name: Calendar description: >- The dated work across your organization in one list, narrowed to the areas your key may read. - name: Activity description: >- What was created, changed and deleted in your organization, narrowed to the areas your key may read. - name: Shift schedules description: >- Schedules: the occasions shifts are grouped under, such as an adoption day or Saturday kennel cover. - name: Shift windows description: >- Shifts: a stretch of time at a place, with the volunteer roles it needs and how many of each (the address calls a shift a window). - name: Shift bookings description: >- Sign-ups: a person taking a role on a shift, giving it up, and the hours they worked. - name: Volunteers description: >- The people who volunteer: where each stands, what they have done, and where they would rather work. - name: Volunteer roles description: >- The jobs a volunteer can sign up for, such as Dog walker or Adoption counselor. - name: Volunteer qualifications description: 'Approvals: who may take which role, and at which location.' - name: Shift policies description: The rules you set for sign-ups and cancellations. - name: Shift calendar description: Schedules and shifts as calendar items for a date range. - name: Shift custom fields description: Your own fields on schedules, shifts and sign-ups. - name: Events description: >- The occasions your rescue hosts: adoption days, fundraisers, clinics and the rest. - name: Events calendar description: Your events between two days, as calendar entries. - name: Campaigns description: >- Appeals you raise money for, each with its goal and what it has raised so far. - name: Donations description: 'Gifts of money: how much, from whom, and what they were given to.' - name: Donors description: The people who have given, with what each has given in all. - name: Wish list description: The things your rescue needs, and the deliveries that met them. - name: Fundraising custom fields description: Your organization's own fields on donations and campaigns. - name: Message templates description: >- Saved wording your organization sends again and again, with merge fields filled from your records. - name: Sending description: >- Everything here sends real email from your organization, and none of it can be unsent. - name: Message log description: >- The email your organization has sent or tried to send, and what became of each message. - name: Conversations description: >- The email conversations in your organization's inboxes, and the records each one is about. - name: Inboxes description: >- The addresses your organization receives email at, and who may read each one. - name: Contact preferences description: >- Whether a person has asked not to be emailed, altogether or about one kind of message. - name: Suppressions description: >- Addresses no email goes to, because mail to them bounced or their owner asked not to be written to. - name: Sender and deliverability description: Who your organization's email goes out as, and how much of it arrives. - name: Registry flags description: >- Safety flags your organization files about a person or an animal, which other organizations using RescueConsole can see once the flag is vetted and shared. - name: Registry reviews description: >- Another organization's vote on a flag it did not file, which decides whether the flag becomes active or disputed. - name: Registry search description: >- The lookup by microchip number that anybody may make, with or without a key. paths: /api/animals/medical/bulk: post: tags: - Medical due summary: Add a record to many animals description: >- Adds the same medical record to up to 100 animals at once, such as a vaccine given at a clinic day. What is the same for every animal goes in record; what is each animal's own (a lot number, a tag number, a test result, a note) goes on that animal's entry and is merged over it. next, when you send it, is the follow-up record and is made on every animal too. All or nothing: every animal's record is checked before any is written. When the record is refused on any animal, nothing is added, and the refusal (400) lists each animal it was refused for in problems, with animal_id, name and error. A record due and not yet done makes a task on each animal, and a spay or neuter procedure that is done updates the animal's altered details. Needs **write** on Animals. operationId: createBulkMedicalRecords requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/MedicalBulkRequest' example: record: record_type: vaccination name: Rabies catalogue_item_id: 8e4035af-8412-4357-a5e6-03d93937b53e performed_on: '2026-09-16' performed_in_house: true details: method: Subcutaneous site: Right hind leg product_expires_on: '2027-03-01' notes: Clinic day next: record_type: vaccination name: Rabies due_on: '2027-09-16' recurrence_interval: 1 recurrence_unit: year animals: - animal_id: 39fbe05a-3fcd-4e02-9091-bde4e4e26098 details: lot_number: L-100 - animal_id: 4a0cf16b-40de-4f13-a1a2-cef5f5f371a9 details: lot_number: L-100 notes: Hissed, fine - animal_id: 5b1d027c-51ef-4024-b2b3-d0a60604820b details: lot_number: L-101 responses: '201': description: Every record was added. content: application/json: schema: type: object required: - created - animals - ids properties: created: type: integer description: How many records were made, the follow-ups included. animals: type: integer description: How many animals. ids: type: array items: type: string description: The new records' IDs. '400': $ref: '#/components/responses/Problem' '401': $ref: '#/components/responses/Problem' '403': $ref: '#/components/responses/Problem' '500': description: >- It stopped part way. The records already made stay; the answer says how many and which, so you can add the rest. content: application/json: schema: type: object required: - error - created - animals - ids properties: error: type: string created: type: integer animals: type: integer ids: type: array items: type: string components: schemas: MedicalBulkRequest: type: object required: - record - animals properties: record: $ref: '#/components/schemas/MedicalBulkRecord' next: oneOf: - $ref: '#/components/schemas/MedicalBulkRecord' - type: 'null' description: >- The follow-up record, such as the next vaccine due, made on every animal as it is. The animals' own details are not added to it. animals: type: array minItems: 1 maxItems: 100 description: The animals, at most 100. An animal named twice is counted once. items: type: object required: - animal_id properties: animal_id: type: string details: type: object additionalProperties: true description: This animal's own details, merged over the record's. notes: type: string description: >- This animal's own note, added on a new line below the record's note. result_status: type: string enum: - pending - normal - abnormal - positive - negative - inconclusive description: This animal's own test result. MedicalBulkRecord: type: object required: - record_type properties: record_type: type: string enum: - vaccination - treatment - procedure - test - medication - exam - condition - preventative name: type: string description: >- What it is, such as Rabies. Required, unless catalogue_item_id gives the item's name. catalogue_item_id: type: string description: >- An item from your medical catalogue of the matching kind: a vaccine for a vaccination, a test for a test, a diagnosis for a condition, a treatment for a treatment, a procedure for a procedure. The other record types cannot name one. performed_on: type: - string - 'null' description: The day it was done. Leave it out for something scheduled. format: date due_on: type: - string - 'null' description: >- The day it is due. A record due and not yet done is scheduled, and makes a task on the animal. format: date due_start_at: type: - string - 'null' description: The time a scheduled item starts, as a date and time. Needs due_on. format: date-time duration_minutes: type: - integer - 'null' description: >- How long it takes, from 5 to 1440 minutes. An hour when there is a start time, it is not done, and you do not say. minimum: 5 maximum: 1440 notes: type: - string - 'null' details: type: object additionalProperties: true description: >- The record's own fields, by key. A vaccination, treatment, exam and procedure have built-in fields (a vaccination has given_at, lot_number, product_expires_on, method and site), and a catalogue item adds its own. When the record names a catalogue item, or its type has built-in fields, only those keys are accepted, each as its field's type: text, a number, true or false, a YYYY-MM-DD date, an HH:MM time, one of the field's options, or a person's ID. Otherwise any key is accepted with a value that is text (up to 2,000 characters), a number, or true or false. Empty values are dropped. result_status: type: string enum: - pending - normal - abnormal - positive - negative - inconclusive description: A test's result. Only on a test. performed_in_house: type: boolean description: Done by your own clinic. Such a record names no outside practice. performed_by_person_id: type: string description: >- Who did it, a person in your organization. The person who made the key, unless you say. veterinary_practice_id: type: string description: The practice, an organization in your organization's records. veterinarian_person_id: type: string description: The vet, a person in your organization. medication_id: type: string description: A medication from your medications list. refills_remaining: type: - integer - 'null' minimum: 0 prescription_expires_on: type: - string - 'null' format: date recurrence_interval: type: - integer - 'null' description: >- With recurrence_unit, how often it repeats: every 1 year, every 3 weeks. Send both or neither. A repeating record needs due_on or performed_on to count from. minimum: 1 recurrence_unit: type: - string - 'null' enum: - day - week - month - year - null responses: Problem: description: What is wrong, in one sentence you can show to a person. content: application/json: schema: type: object required: - error properties: error: type: string example: error: house_trained must be 1, 0 or null (not assessed) securitySchemes: apiKey: type: http scheme: bearer description: An API key from Settings, API keys. It starts with rc_live_. ````