KPMG Locations API

openapi: 3.2.0
info:
  title: KPMG Origins Locations API
  description: '- How to authenticate

    - Definitions of Key API Endpoints

    - Other Information


    KPMG Origins provides customers with access to their data, and data shared with them, through APIs. The APIs allow customers with the ability to create, update and extract available data.


    ## How to authenticate

    1) Create API credentials via KPMG Origins UI (NB: only users with the Administrator role can manage API credentials):

    - Login to KPMG Origins

    - Go to Settings page, then API Credentials tab

    - Create API credentials

    - Copy the Client Id and Secret (NB: you will not be able to recover the secret value if lost, however, you can generate a new one)

    2) Exchange API Credentials for a short-lived _access token_

    - Make a POST request to **https://<KPMG Origins hostname>/cr/client-api/v1/token**

    ```

    {

    "clientId": "",

    "secret": ""

    }

    ```

    3) Make authenticated requests to KPMG Origins API:

    - Use the access token value form the token API response as a Bearer token to make requests to the API i.e. set Authorization header like this: `Authorization: Bearer `

    ```

    NB: access token is only valid for a short time, if requests start failing with 401 status code, repeat steps 2) and 3)

    ```


    ## Definitions of Key API Endpoints


    This section explains key definitions of key data entities and API endpoints


    * **Organisation**: the organisation can either be an organisation or an individual.

    - An *organisation* is a participant which usually holds an ABN or ACN, usually an entity participating in commercial activities.

    - An *individual* is a participant who has no ABN or ACN. For example, in Movement, a generator who is a private individual (e.g. residential asbestos pick-up).


    This distinction is necessary as it relates to a validation in the ``post organisation`` API.

    * **Location**: locations represent geographical sites which are operated by organisations. Each location possesses a unique location ID to distinguish it from other locations in the system, as well as an organisation / client ID that specifies which organisation operates it.


    Please see the details on each individual API to learn more about the specific criteria needed for a successful payload.


    ## Other Information

    - The format for Client Id mentioned in the APIs is ``IDType.IDValue``

    - By default, the collection of items returned can include up to 10,000 items, but this can be changed via the ``Limit`` and ``Skip`` parameters.'
  version: '1.0'
tags:


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