> ## 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. # Approve or reject a submission > Records the answer on an adoption application, a foster application or a volunteer sign-up; other kinds are not decided. Not on spam: mark it not spam first. Send `decision: null` to undo a decision. When the answer changes: a submission still new is marked reviewed, a hold is taken off, and any workflow your organization set to run on that answer starts, for the person the submission belongs to (a submission with no person yet starts it when it is converted). Sending the same answer again changes only the note. If an adoption or foster application was made from the submission, it takes the same answer: approved, denied, or back to submitted on an undo. Needs **write** on the area of the form's kind. ## OpenAPI ````yaml /api-reference/openapi.json post /api/forms/submissions/{id}/decision 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/forms/submissions/{id}/decision: parameters: - name: id in: path required: true description: The submission's record ID. schema: type: string post: tags: - Submissions summary: Approve or reject a submission description: >- Records the answer on an adoption application, a foster application or a volunteer sign-up; other kinds are not decided. Not on spam: mark it not spam first. Send `decision: null` to undo a decision. When the answer changes: a submission still new is marked reviewed, a hold is taken off, and any workflow your organization set to run on that answer starts, for the person the submission belongs to (a submission with no person yet starts it when it is converted). Sending the same answer again changes only the note. If an adoption or foster application was made from the submission, it takes the same answer: approved, denied, or back to submitted on an undo. Needs **write** on the area of the form's kind. operationId: decideSubmission requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/SubmissionDecision' example: decision: approved note: Home visit went well. Fenced yard, two older children. responses: '200': description: The submission, as Get one submission gives it. content: application/json: schema: $ref: '#/components/schemas/SubmissionDetail' '400': $ref: '#/components/responses/Problem' '401': $ref: '#/components/responses/Problem' '403': $ref: '#/components/responses/Problem' '404': $ref: '#/components/responses/Problem' components: schemas: SubmissionDecision: type: object required: - decision properties: decision: type: - string - 'null' enum: - approved - rejected - null description: null undoes the decision, and its note. note: type: - string - 'null' maxLength: 2000 SubmissionDetail: type: object required: - submission - fields - can_write - can_decide properties: submission: allOf: - $ref: '#/components/schemas/Submission' - type: object properties: animals: type: array description: >- The animals the applicant picked, as they are now. One deleted since is left out. items: type: object properties: id: type: string name: type: - string - 'null' species: $ref: '#/components/schemas/Species' decided_by_name: type: - string - 'null' description: Who decided, by name. fields: type: array description: >- The form's questions as they are today, in order, to label the answers. An answer to a question removed since has no label here. items: type: object required: - field_key - label properties: field_key: type: string label: type: string can_write: type: boolean description: Whether your key may change it. can_decide: type: boolean description: Whether it is a kind that is approved or rejected. Submission: type: object description: >- One submission. The list also carries the form's title, address and kind, the application made from it, and the assignees; changing one returns the submission alone. additionalProperties: true required: - id - form_id - answers - status - submitted_at properties: id: type: string form_id: type: string answers: type: object description: >- What the person sent, as text, keyed by each question's field_key. Only questions the form asked are kept. An answer to a question removed since is still here. additionalProperties: type: string animal_ids: type: array description: >- The record IDs of the listed animals the applicant picked, in the order they picked them. items: type: string submitter_name: type: - string - 'null' description: The sender's name, taken from the answers. submitter_email: type: - string - 'null' description: The sender's email, taken from the answers. status: $ref: '#/components/schemas/SubmissionStatus' notes: type: - string - 'null' description: Your team's notes. reviewed_by_person_id: type: - string - 'null' reviewed_at: type: - string - 'null' format: date-time converted_to_type: type: - string - 'null' description: person once the submission is joined to one. converted_to_id: type: - string - 'null' description: The record ID of the person it is joined to. converted_how: type: - string - 'null' enum: - created - linked - null description: >- created when the person was made from this submission, linked when they were already on file. A submission with an email is joined to a person by itself when it arrives: to the person with that email, or to a new one. decision: type: - string - 'null' enum: - approved - rejected - null description: Null until somebody decides, and after a decision is undone. decided_at: type: - string - 'null' format: date-time decided_by_person_id: type: - string - 'null' decision_note: type: - string - 'null' held_at: type: - string - 'null' format: date-time description: When a failed check in a workflow put it on hold. hold_reason: type: - string - 'null' application_id: type: - string - 'null' description: The adoption or foster application made from it. submitted_at: type: string format: date-time updated_at: type: - string - 'null' format: date-time form_title: type: string description: On the list, one submission, and convert. form_slug: type: string description: On the list, one submission, and convert. form_kind: $ref: '#/components/schemas/FormKind' application_status: type: - string - 'null' description: >- Where the application made from it stands, such as submitted, approved or denied. On the list and one submission. application_stage: type: - string - 'null' description: The application's stage key. On the list and one submission. application_stage_label: type: - string - 'null' description: The stage in your organization's words. assignees: type: array description: >- Who is working it, in the order they were assigned. On the list and one submission. items: $ref: '#/components/schemas/SubmissionAssignee' Species: type: string enum: - dog - cat - rabbit - equine - small_mammal - large_mammal - bird - barnyard - fish - reptile - exotic SubmissionStatus: type: string description: >- new until somebody reviews it; reviewed; converted once somebody converts it (see Convert a submission); spam, which is kept but left out of the list unless you ask for it. A submission caught by the spam trap on your public form arrives as spam. A submission joined to a person by itself when it arrived stays new, because nobody has reviewed it yet. enum: - new - reviewed - converted - spam FormKind: type: string description: >- What a form is for, which decides the area its submissions belong to and so which keys may read them. adoption_application, foster_application and surrender (a surrender request) are Animals; volunteer (a volunteer sign-up) is Shifts; donor is Fundraising; contact and general are People. enum: - adoption_application - foster_application - volunteer - donor - surrender - contact - general SubmissionAssignee: type: object required: - person_id - name properties: person_id: type: string name: type: string 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_. ````