> ## Documentation Index
> Fetch the complete documentation index at: https://docs.frankieone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Continuous KYB for Australian Organizations

> Turn Continuous KYB monitoring on or off for an Australian organization with the FrankieOne v2 API, and receive notifications when its registered business details change.

Continuous KYB monitors an Australian organization after onboarding and notifies you when its registered business details change, including credit score changes. This page is for developers integrating with the FrankieOne v2 API. It covers how to turn monitoring on or off for an organization and what the API returns.

Applies to FrankieOne KYB v2, for organizations registered in Australia. For the v1 API, see [Continuous KYB for an Entity](/docs/v1/kyb/australian/continuous-kyb).

## Before you start

* Continuous KYB must be turned on for your customer account. If it is not, requests for this monitoring type return `403`. To turn it on, reach out to your Customer Success Manager.
* The organization must already exist in FrankieOne. See [Creating & Managing Organizations](/docs/kyb/managing-organizations) to create one and get its `entityId`.
* The organization must be registered in Australia and have a valid ABN or ACN. Monitoring does not apply to deleted organizations.

## How Continuous KYB works

<Steps>
  <Step title="Turn on monitoring">
    Send one API request to turn on Continuous KYB for the organization. FrankieOne registers the organization's ABN or ACN for monitoring and creates a `CONTINUOUS_KYB_AU` subscription on its service profile.
  </Step>

  <Step title="FrankieOne monitors the organization">
    FrankieOne checks for changes to the organization's registered details. You don't need to take any further action.
  </Step>

  <Step title="Receive notifications">
    When a change is detected, FrankieOne sends a notification to your configured webhook.
  </Step>
</Steps>

## Turn monitoring on or off

Use the [Turn on/off monitoring for a given organization](/api-reference/organization-monitoring/turn-onoff-monitoring-for-a-given-organization) endpoint with `monitoringTypes=CONTINUOUS_KYB_AU`.

**Endpoint:** `PATCH /v2/organizations/{entityId}/monitor`

**Query parameters:**

| Parameter | Type | Required | Description |
| :- | :- | :- | :- |
| `enabled` | boolean | Yes | Set to `true` to turn monitoring on, or `false` to turn it off. |
| `monitoringTypes` | array of strings | No | The monitoring types to change. Use `CONTINUOUS_KYB_AU` for Continuous KYB. |

You can include a `comment` in the request body. FrankieOne adds it to the organization's audit log.

### Example: turn on Continuous KYB

<CodeGroup>
  ```bash Request - Turn on Continuous KYB theme={null}
  curl --location --request PATCH 'https://api.uat.frankie.one/v2/organizations/019931f9-02a2-7c87-816c-c9e6743eaae5/monitor?enabled=true&monitoringTypes=CONTINUOUS_KYB_AU' \
  --header 'api_key: YOUR_API_KEY' \
  --header 'X-Frankie-CustomerId: YOUR_CUSTOMER_ID' \
  --header 'Content-Type: application/json' \
  --data '{
      "comment": {
          "text": "Monitoring turned on after onboarding approval"
      }
  }'
  ```
</CodeGroup>

#### Response

A successful request returns `200 OK`. The `monitoring.CONTINUOUS_KYB_AU` object shows the subscription status. It is present only when Continuous KYB is turned on for your account and the request included `CONTINUOUS_KYB_AU`.

<CodeGroup>
  ```json Response - 200 OK theme={null}
  {
      "requestId": "01HN9XHZN6MGXM9JXG50K59Q85",
      "monitoring": {
          "CONTINUOUS_KYB_AU": {
              "status": "ENABLED",
              "providers": [
                  "creditorwatch"
              ],
              "subscriptions": [
                  {
                      "serviceName": "KYB",
                      "serviceProfileId": "0199320a-5b1e-7d4a-9c2f-3e8a6b1d2c40",
                      "status": "ENABLED",
                      "enabledAt": "2026-09-30T05:18:16Z",
                      "enabledRequestId": "01HN9XHZN6MGXM9JXG50K59Q85",
                      "enabledBy": "example@frankieone.com"
                  }
              ]
          }
      }
  }
  ```
</CodeGroup>

| Field | Description |
| :- | :- |
| `status` | `ENABLED` when the organization is being monitored, or `DISABLED` when it is not. |
| `providers` | The providers affected by the subscription. |
| `subscriptions` | One entry for the organization's KYB service profile, with the times and request IDs of the last change. |

### Example: turn off Continuous KYB

Send the same request with `enabled=false`. The subscription status changes to `DISABLED`, and FrankieOne stops sending notifications for the organization.

<CodeGroup>
  ```bash Request - Turn off Continuous KYB theme={null}
  curl --location --request PATCH 'https://api.uat.frankie.one/v2/organizations/019931f9-02a2-7c87-816c-c9e6743eaae5/monitor?enabled=false&monitoringTypes=CONTINUOUS_KYB_AU' \
  --header 'api_key: YOUR_API_KEY' \
  --header 'X-Frankie-CustomerId: YOUR_CUSTOMER_ID'
  ```
</CodeGroup>

### Turning on monitoring that is already on

If Continuous KYB is already turned on for the organization, a request with `enabled=true` returns `200 OK` with the current subscription. It does not create a second subscription.

## Automatic unsubscribe

To optimize your costs, FrankieOne automatically disables Continuous KYB for an organization when:

* The organization is deleted.
* The organization's KYB service profile is archived or becomes inactive.

## Related pages

* [Event Notifications & Webhooks](/docs/reference/webhooks): how to set up a webhook endpoint with FrankieOne.
* [Creating & Managing Organizations](/docs/kyb/managing-organizations): create an organization and get its `entityId`.
* [Continuous KYB for an Entity (v1)](/docs/v1/kyb/australian/continuous-kyb): the v1 subscription endpoint.