Gingr

Gingr Pets API

Pet profiles belonging to an owner.

GitHub OpenAPI

Operations 24

GET /v1/pets/{petId}/immunizations Pets Immunizations - List #
PUT /v1/pets/{petId}/immunizations/{immunizationTypeId} Pets Immunizations - Update #
POST /v1/pets/{petId}/pet-notes Pet Employee Notes - Create #
PUT /v1/pets/{petId}/pet-notes/{noteId} Pet Employee Notes - Update #
GET /v1/pets Pets - List #
POST /v1/pets Pets - Create #
GET /v1/pets/{petId} Pets - Details #
PUT /v1/pets/{petId} Pets - Update #
DELETE /v1/pets/{petId} Pets - Delete #
POST /v1/pets/merge Pets - Merge #
GET /v1/pets/last-service-duration Pet Service Type - Last Duration #
GET /v1/pets/last-service-price Pet Service - Last Price #
GET /v1/pets/{petId}/feeding Pets Feeding - Details #
POST /v1/pets/{petId}/feeding Pet Feeding - Create #
PUT /v1/pets/{petId}/feeding/{feedingId} Pet Feeding - Update #
DELETE /v1/pets/{petId}/feeding/{feedingId} Pets Feeding - Delete #
GET /v1/pets/immunization/expired Pet Immunizations - List Expired #
GET /v1/pets/{petId}/medications Pets Medications - Details #
POST /v1/pets/{petId}/medications Medications - Create #
PUT /v1/pets/{petId}/medications/{medicationId} Pet Medications - Update #
DELETE /v1/pets/{petId}/medications/{medicationId} Pet Medication Schedule - Delete #
GET /v1/pets/{petId}/report-cards Pets Report Cards - List #
GET /v1/pets/{petId}/report-cards/{reportCardId} Report Cards - Details #
GET /v1/pets/report-card-media Report Card Media - List #

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-pets-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-pets-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-pets-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Gingr Pets 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 (150 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/gingr/refs/heads/main/openapi/gingr-pets-api-openapi.yml