Gingr

aid: gingr
url: https://raw.githubusercontent.com/api-evangelist/gingr/refs/heads/main/apis.yml
name: Gingr
kind: company
description: Gingr is pet-care business management software for dog daycare, boarding, training, and grooming facilities,
  covering reservations, check-in/checkout, client and pet records, feeding and medication schedules, immunizations, report
  cards, point of sale, and payments. Gingr publishes a JSON:API-style Partner API (api.gingr.io, X-Api-Key header, live OpenAPI/Swagger
  and Postman collection at docs.gingr.io) covering owners (parents), pets, bookings/reservations, invoices and payments,
  immunizations, and report cards, alongside an older subdomain-scoped legacy reporting API used for read-only pulls of owners
  and reservations.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/gingr.png
tags:
- Pet Care
- Pet Daycare
- Boarding
- Grooming
- Vertical SaaS
- Scheduling
- Payments
created: '2026-07-04'
modified: '2026-07-04'
specificationVersion: '0.23'
apis:
- aid: gingr:gingr-invoices-api
  name: Gingr Invoices API
  description: Invoices and charges.
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Invoices
  properties:
  - type: OpenAPI
    url: openapi/gingr-invoices-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
- aid: gingr:gingr-payments-api
  name: Gingr Payments API
  description: Charging and refunding cards on file, invoices, and deposits.
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/gingr-payments-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
- aid: gingr:gingr-pets-api
  name: Gingr Pets API
  description: Pet profiles belonging to an owner.
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Pets
  properties:
  - type: OpenAPI
    url: openapi/gingr-pets-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
- aid: gingr:gingr-booking-type-rates-api
  name: Gingr Booking Type Rates API
  description: Booking Type Rates
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Booking Type Rates
  properties:
  - type: OpenAPI
    url: openapi/gingr-booking-type-rates-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
- aid: gingr:gingr-bookings-api
  name: Gingr Bookings API
  description: 'The **Bookings** group is the core of the Gingr API. A **Booking** (also called a Reservation internally)
    represents a scheduled service for one or more animals at a specific location and time.


    The typical booking lifecycle is:


    1. **Validate** — Call the validation endpoints to check availability and confirm there are no conflicts before committing.

    2. **Create** — Submit the booking with the required fields. The response includes the new booking ID.

    3. **Pre-check** — If the organization requires a pre-check, retrieve the pre-check form (`GET /v1/bookings/{id}/precheck-form`)
    and submit answers (`POST /v1/bookings/{id}/precheck`).

    4. **Accept / Confirm** — Some organizations require staff to manually confirm bookings. Use the accept endpoint when
    `manualConfirm` is enabled.

    5. **Checkout** — When the service is complete, submit payment via the checkout endpoint.

    6. **Cancel** — If needed, cancel the booking and optionally apply a cancellation fee.


    Key concepts:


    - **`manualConfirm`** — When this flag is `true` on a booking type, new bookings land in a "pending" state and must be
    explicitly accepted by staff before they are considered confirmed. If `false`, bookings are auto-confirmed.

    - **Overrides** — The `overrides` object in the create/update requests lets you bypass certain business rule validations
    (e.g., overbooking a run, scheduling outside business hours). Overrides require elevated API permissions and should be
    used sparingly.

    - **Services** — A booking can have one or more services attached (e.g., the base boarding service plus grooming add-ons).
    Services carry their own pricing and scheduling.

    - **Lodging** — For overnight boarding, the booking is assigned to a specific run/kennel. The available lodgings endpoint
    returns which runs are open for the requested dates.

    - **Pre-check** — A digital check-in form that collects health, feeding, and care instructions for the animal''s stay.
    Whether pre-check is required depends on organization settings.

    - **Standing Bookings** — Recurring bookings on a fixed schedule (e.g., every Monday for daycare). Changes to a standing
    booking can apply to the single instance or all future occurrences.'
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Booking
  tags_raw:
  - Bookings
  properties:
  - type: OpenAPI
    url: openapi/gingr-bookings-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
- aid: gingr:gingr-card-on-file-api
  name: Gingr Card On File API
  description: 'The **Card On File** group manages saved payment methods for a parent. Gingr stores tokenized card details
    through its payment gateway integration — raw card numbers are never stored or transmitted through the API.


    Use this group to:


    - **List** saved cards for a parent.

    - **Set a default** card to use for auto-billing and deposits.

    - **Delete** a card that is no longer needed.

    - **Initiate card capture** flows for parents who need to add a new card.


    Cards on file are required for certain features such as automatic deposits, membership auto-billing, and one-click checkout.'
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Card on File
  tags_raw:
  - Card On File
  properties:
  - type: OpenAPI
    url: openapi/gingr-card-on-file-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
- aid: gingr:gingr-config-api
  name: Gingr Config API
  description: 'The **Config** group exposes read and write endpoints for all organization-level configuration data in Gingr.
    This includes the lookup tables and settings that everything else depends on — species, breeds, booking types, service
    options, feeding options, immunization types, forms, locations, hours of operation, tax rates, areas, disabled dates,
    and more.


    Typically you will call these endpoints once at startup (or on a periodic refresh) to build local caches that your integration
    can reference when creating bookings, parents, and pets. Most config data changes infrequently and is safe to cache for
    hours or even days.


    Key things to know:


    - **Booking Types** define the kinds of services a location offers (e.g., Boarding, Daycare, Grooming). A booking must
    reference a valid booking type for the target location.

    - **Service Options** are add-ons that can be attached to a booking (e.g., extra walks, nail trim). Each service option
    belongs to a booking type.

    - **Forms** are questionnaires associated with bookings or animals. Form answers are collected during the pre-check process.

    - **Areas / Runs** represent physical kennel spaces. Lodging availability and capacity constraints live here.

    - **Tax Rates** define the tax rules applied when invoicing. Whether tax is applied to a booking depends on organization
    settings.

    - **Disabled Dates** let you know when a location is closed so you can avoid booking on those days.'
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Config
  properties:
  - type: OpenAPI
    url: openapi/gingr-config-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
- aid: gingr:gingr-group-classes-api
  name: Gingr Group Classes API
  description: 'The **Group Classes** group manages enrollment in structured group training and activity sessions. Unlike
    individual bookings, group classes have a fixed schedule, a capacity limit, and a roster of enrolled animals.


    Use this group to list available class sessions, check capacity, enroll an animal, and retrieve class rosters. Pricing
    for group classes is set at the class-type level in the Config group.'
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Group Classes
  properties:
  - type: OpenAPI
    url: openapi/gingr-group-classes-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
- aid: gingr:gingr-parents-api
  name: Gingr Parents API
  description: 'The **Parents** group covers everything related to the pet owner — referred to as a **Parent** in Gingr. A
    Parent is the primary account holder who owns one or more animals and makes bookings.


    Use this group to:


    - **Create** new parents during the intake flow (e.g., an online booking portal).

    - **Update** parent profile data such as contact info, address, and custom fields.

    - **Search / list** parents by name, email, phone, and other filters.

    - **Manage memberships** — enroll or cancel a parent''s membership plan.

    - **Manage cards on file** — retrieve saved payment methods so you can pre-fill checkout forms.

    - **Handle agreements** — check which digital waivers a parent still needs to sign and mark them as signed.


    Important considerations:


    - `email` and `cellPhone` are unique per organization. Attempting to create a duplicate will return a `422` validation
    error.

    - `allowOnlineLogin` controls whether the parent can log in to the Gingr consumer portal. This defaults to `false` for
    API-created parents unless explicitly set.

    - Custom fields (configured per organization) can be passed in the `customFields` object. Field keys vary by organization
    — use the Config `/v1/config` endpoint or contact support to get the key names for a specific subdomain.'
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Parents
  properties:
  - type: OpenAPI
    url: openapi/gingr-parents-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
- aid: gingr:gingr-payment-api
  name: Gingr Payment API
  description: Payment
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Payments
  tags_raw:
  - Payment
  properties:
  - type: OpenAPI
    url: openapi/gingr-payment-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
- aid: gingr:gingr-precheck-api
  name: Gingr Precheck API
  description: 'The **Precheck** group handles the digital pre-check-in process for bookings. A pre-check collects animal
    care instructions — feeding, medications, behavioral notes, and custom form answers — before the animal arrives for its
    stay.


    Whether pre-check is required depends on the organization''s settings and the booking type. When required, a booking cannot
    be fully confirmed until a pre-check has been submitted.


    Use this group to retrieve the pre-check form definition for a booking and to submit completed form answers.'
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Precheck
  properties:
  - type: OpenAPI
    url: openapi/gingr-precheck-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
- aid: gingr:gingr-upload-api
  name: Gingr Upload API
  description: 'The **Upload** group provides endpoints for attaching files to parent and pet records. Supported file types
    include images (profile photos) and documents (vaccination certificates, signed waivers, etc.).


    Uploaded files are stored in Gingr''s file storage and associated with the relevant parent or pet record. File size and
    type restrictions apply — see individual endpoint documentation for limits.'
  humanURL: https://support.gingrapp.com/hc/en-us/articles/25722122517517-Gingr-API-Functions-Reference
  baseURL: https://api.gingr.io/v1
  tags:
  - Upload
  properties:
  - type: OpenAPI
    url: openapi/gingr-upload-api-openapi.yml
  - type: Documentation
    url: https://docs.gingr.io/documentation
  - type: Documentation
    url: https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API
common:
- type: CapabilityMap
  url: capabilities/gingr-capability-edges.yml
  name: Gingr Business Capability Map
- type: AgenticAccess
  url: agentic-access/gingr-agentic-access.yml
- type: DomainSecurity
  url: security/gingr-domain-security.yml
- type: Authentication
  url: authentication/gingr-authentication.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/gingr-llc
- type: Website
  url: https://www.gingrapp.com
- type: Documentation
  url: https://support.gingrapp.com/hc/en-us
- type: Plans
  url: plans/gingr-plans-pricing.yml
- type: RateLimits
  url: rate-limits/gingr-rate-limits.yml
- type: FinOps
  url: finops/gingr-finops.yml
- url: https://www.gingrapp.com/blog
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com