API & integrations · Article 2 of 6

NDIS API — setup

Setting up the NDIS integration is an admin task run once per account. This article covers what you provide, how it's stored, and the feature flags that control how much automation runs on top.

4 min read Last updated April 2026

Who runs the setup

An account administrator runs this once per Navigator account. You need:

The account.update permission in Navigator
A PRODA activation code for your organisation (from the NDIS)
A device name (you choose this — it identifies this Navigator account to the NDIS)
Your registration authority code from the NDIS

The code is a one-time token — once exchanged, it's gone. You can't re-use the same activation code to set up a second account.

Where to find the setup

Go to Settings → PRODA. You'll see the activation form if the integration isn't set up yet, or a status page if it is.

What you provide

Field	What it's for
Device name	A label for this Navigator account's connection to the NDIS. Purely for your reference — shown in PRODA device management.
Registration authority	Your NDIS provider registration authority code.
Activation code	The one-time code you generate in PRODA to authorise a new device. Single use.

How activation works

You submit the three fields above.
Navigator exchanges the activation code with the NDIS and receives a long-lived authentication token.
The token is encrypted and stored against your account. Navigator uses it for every subsequent call — you don't handle it directly.
The account becomes live on the NDIS integration. Claims can be submitted and plan data can be synced.

Token is never visible The authentication token is encrypted at rest and never shown in the UI. If the token is lost or invalidated, you'll need a fresh PRODA activation code — the only way to recover the connection.

Feature flags that control automation

Four account-level feature flags control how much automation runs on top of the raw integration. These are managed by your Kismet contact, not visible in the normal settings UI.

Flag	What it controls
`ndis_api`	Master switch. Turns the NDIS integration on or off for the whole account. Must be on for anything else to work.
`ndis_api_pace_notifications`	Enables receiving PACE events (relationship changes, plan approvals, budget updates). Without this, only PRODA transactional flows work.
`ndis_api_remittance_advice_notification`	Enables automatic processing of remittance advice — invoice payment dates are updated as the NDIS pays claims.
`ndis_api_notification_automation`	When on, PACE events auto-sync and log. When off, they create tasks for manual review. See Syncing funds & plans.

All new features are off by default when released, and your Kismet contact enables them once you're ready to adopt them.

Disabling the integration

If you need to disconnect from the NDIS API — for example, if your organisation is winding down an account or moving to a different PRODA device — your administrator can disable it from the same PRODA settings page. When disabled:

All three stored fields (device name, registration authority, token) are cleared.
Navigator stops sending and receiving NDIS API traffic for this account.
Previously-submitted claims and synced data remain in Navigator — they're not rolled back.

To re-enable, you need a fresh PRODA activation code and to start the setup from scratch.