KPMG

KPMG Registries API

The Registries API from KPMG — 2 operation(s) for registries.

GitHub OpenAPI

Operations 2

GET /cr/client-api/v1/swagger.json Registries API v1 Swagger document #
GET /cr/client-api/swagger/ Registries API Swagger UI #

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/kpmg/refs/heads/main/openapi/kpmg-registries-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/kpmg-registries-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

kpmg-registries-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: KPMG Origins Registries API
  version: '1.0'
  description: "KPMG Origins is the public-facing platform implementing the NSW\nIntegrated Waste Tracking System (IWTS) and is the single discoverable\npublic REST API surface inside the KPMG brand. It exposes two API\nfamilies:\n\n  * Movements API   - waste-movement reporting (Swagger v1, v2, v3, v4)\n  * Registries API  - organisations and locations (Swagger v1)\n\nA representative subset of endpoints from each family is included\nhere. Authentication uses an operator-generated API access key,\ndocumented at the integration guide URL below.\n"
  contact:
    name: Kin Lane
    email: kin@apievangelist.com
    url: https://apievangelist.com
  license:
    name: Documentation reference only
    url: https://help.kpmgorigins.com/en/articles/1850-integrating-with-origins
servers:
- url: https://app.kpmgorigins.com
  description: Production
- url: https://sandbox.app.kpmgorigins.com
  description: Sandbox
security:
- ApiKeyAuth: []
tags:
- name: Registries
paths:
  /cr/client-api/v1/swagger.json:
    get:
      summary: Registries API v1 Swagger document
      operationId: registriesV1Swagger
      tags:
      - Registries
      responses:
        '200':
          description: Registries API v1 Swagger 2.0 document
          content:
            application/json:
              schema:
                type: object
  /cr/client-api/swagger/:
    get:
      summary: Registries API Swagger UI
      operationId: registriesSwaggerUi
      tags:
      - Registries
      responses:
        '200':
          description: Swagger UI HTML
          content:
            text/html:
              schema:
                type: string
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: 'Operator-generated API access key from KPMG Origins account

        settings. The integration guide describes the key as required

        for all calls to the client-api surface; see

        https://help.kpmgorigins.com/en/articles/1850-integrating-with-origins

        '
externalDocs:
  description: KPMG Origins integration guide
  url: https://help.kpmgorigins.com/en/articles/1850-integrating-with-origins