Gingr

Gingr Parents API

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.

GitHub OpenAPI

Operations 45

POST /v1/parents/{parentId}/sign-agreements/{agreementId} Parent - Sign Agreement #
GET /v1/parents/{parentId}/unsigned-agreements Parent - Unsigned Agreements #
GET /v1/parents/{parentId}/signed-agreements Parent - Signed Agreements #
GET /v1/parents/open-balance Parent - Open Balance #
GET /v1/parents/{parentId}/card-on-file Card On File - Show #
POST /v1/parents/{parentId}/card-on-file Card On File - Add #
DELETE /v1/parents/{parentId}/card-on-file Card On File - Delete #
PUT /v1/parents/{parentId}/card-on-file/{cardId} Card On File - Update #
POST /v1/parents/{parentId}/parent-notes Parent Employee Notes - Create #
PUT /v1/parents/{parentId}/parent-notes/{noteId} Parent Employee Notes - Update #
GET /v1/parents/{parentId} Parents - Details #
PUT /v1/parents/{parentId} Parents - Update #
DELETE /v1/parents/{parentId} Parents - Delete #
GET /v1/parents/online-status Parents - Online Status #
GET /v1/parents/validate-phone Parent - Validate Phone #
GET /v1/parents/validate-email Parent - Validate Email #
GET /v1/parents Parents - List #
POST /v1/parents Parents - Create #
GET /v1/parents/unsigned-agreements/{agreementTypeId} Parents - Unsigned Agreements by Type #
GET /v1/parents/{parentId}/parent-files Parent Files - List #
POST /v1/parents/{parentId}/parent-files Parents - Upload File #
GET /v1/parents/parent-files Parent Files - Search #
POST /v1/parents/merge Parents - Merge #
GET /v1/parents/{parentId}/parent-subscriptions Parents - Subscriptions #
POST /v1/parents/{parentId}/parent-subscriptions Parent Subscriptions - Create #
POST /v1/parents/{parentId}/parent-memberships Parents - Enroll Membership #
GET /v1/parents/{parentId}/booking-types/{bookingTypeId}/rates Parents - Booking Type Rate #
GET /v1/parents/parent-memberships Parent Memberships - List #
GET /v1/parents/parent-memberships/{parentMembershipId} Parent Memberships - Detail #
DELETE /v1/parents/parent-memberships/{parentMembershipId} Parent Memberships - Cancel #
GET /v1/parents/parent-packages Parent Packages - List #
GET /v1/parents/parent-packages/{parentPackageId} Parent Package - Details #
POST /v1/parents/{parentId}/parent-packages Parent Packages - Purchase #
GET /v1/parents/{parentId}/preferences Parents Preferences - Details #
PUT /v1/parents/{parentId}/preferences Parents Preferences - Update #
GET /v1/parents/{parentId}/custom-rates Parent - Custom Rates #
GET /v1/parents/{parentId}/reward-points Parent - Reward Points #
POST /v1/parents/{parentId}/reward-points Reward Points - Add #
GET /v1/parents/reward-points-redemption Reward Points Redemption - List #
DELETE /v1/parents/{parentId}/reward-points/{points} Parent Reward Points - Delete #
POST /v1/parents/{parentId}/reward-points/redeem Reward Points - Redeem #
POST /v1/parents/{parentId}/store-credit Store Credit - Add #
GET /v1/parents/store-credit Store Credit - List #
GET /v1/parents/{parentId}/store-credit/balance Store Credit - Remaining Balance #
GET /v1/parents/subscriptions/{subscriptionId} Subscription - Details #

Documentation

📖
Documentation
https://docs.gingr.io/documentation
📖
Documentation
https://support.gingrapp.com/hc/en-us/sections/26779521691661-Gingr-s-API

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/gingr/refs/heads/main/openapi/gingr-parents-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/gingr:gingr-parents-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

gingr-parents-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Gingr Parents API
  description: 'Welcome to the **Gingr API** — a RESTful JSON:API-compliant interface for integrating with Gingr, the leading pet-care business management platform.


    ## Authentication


    All requests require an API key passed in the `X-Api-Key` header. Keys are scoped to a specific organization and can be generated from the Gingr admin dashboard under **Settings → Integrations → API Keys**.


    ## Subdomain Header


    Every request must also include a `subdomain` header identifying which Gingr account you are operating on. This value is the subdomain portion of your Gingr URL (e.g., `mykennel` for `mykennel.gingrapp.com`).


    ## Response Format


    The API follows the JSON:API v1.0 specification. All requests must include:


    ```

    Accept: application/vnd.api+json

    ```


    POST/PUT/PATCH requests that include a body must also include:


    ```

    Content-Type: application/vnd.api+json

    ```


    Paginated list responses include a `meta` object with `currentPage`, `lastPage`, `perPage`, and `total`, as well as a `links` object with `first`, `last`, `prev`, and `next` cursor URLs.


    ## Error Handling


    | HTTP Status | Meaning |

    |-------------|---------|

    | 200 | Success |

    | 201 | Resource created |

    | 400 | Bad request / business logic error |

    | 401 | Unauthorized — invalid or missing API key |

    | 403 | Forbidden — valid key but insufficient permissions |

    | 404 | Resource not found |

    | 422 | Validation error — see `errors` array in response |

    | 500 | Internal server error |


    Validation errors (`422`) are returned as a JSON:API `errors` array where each item contains a `title` and a `detail` describing the offending field.


    ## Rate Limiting


    API requests are subject to rate limiting. Exceeding the limit returns a `429 Too Many Requests` response. Contact Gingr support to discuss higher rate limits for high-volume integrations.'
  version: 1.9.2
tags:


# --- truncated at 32 KB (269 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/gingr/refs/heads/main/openapi/gingr-parents-api-openapi.yml