API & integrations · Article 1 of 6
NDIS API — overview
Navigator connects to the NDIS through two APIs — PRODA (the older system) and PACE (the newer one). Both pass through a single gateway inside Navigator. This article explains which API does what, and which events and flows come from each.
The two NDIS APIs
The NDIS operates two provider-facing APIs:
- PRODA — the legacy system. Still in use for many operational flows.
- PACE — the newer platform. Used for plan management relationship, plan approval, and richer event notifications.
Navigator talks to both APIs through a single internal gateway (the Paradox integration). You don't choose which API to use for a given operation — Navigator picks the right one based on the operation and the participant's plan type. For your team, the two APIs look like one system.
What this article gives you: a clear picture of which API does what, so when a task or note mentions "PACE" or "PRODA", you know where the data came from.
Capability matrix — what each API does
| Capability | PRODA | PACE |
|---|---|---|
| Syncing funds and budgets | Yes | Yes |
| Retrieving participant plans | Yes | Yes |
| Submitting claims (payment requests) | Yes | Yes |
| Remittance advice (payment status) | Yes | Yes |
| Service bookings | Yes | Yes |
| Plan manager relationship events (new / ended) | — | Yes |
| Plan approval notifications | — | Yes |
| Budget updated notifications | — | Yes |
| Plan variation / extension / renewal events | — | Yes |
The short version: PRODA handles the transactional side (claims and fund queries) and PACE adds the event-driven side (automatic notifications when something about the participant's plan or plan management relationship changes).
NDIS events Navigator listens for
PACE sends Navigator webhook notifications when certain things happen on a participant's plan. Each event triggers a specific workflow.
| Event | What it means | Related article |
|---|---|---|
RLTN_CREATED | A plan manager relationship was created or changed for a participant | New & ended relationships |
RLTN_END_DATE_UPDATED | A plan manager relationship end date was updated | New & ended relationships |
PACE_PLAN_APPROVED | A plan was approved by the NDIS | Syncing funds & plans |
BUDGET_UPDATED | A budget changed on an existing plan | Syncing funds & plans |
PACE_VARIATION | Plan details were varied | Syncing funds & plans |
PACE_EXTENSION | Plan was extended | Syncing funds & plans |
PACE_RENEWAL | Plan was renewed | Syncing funds & plans |
REMIT_ADV_GENERATED | Payment remittance advice was generated for a claim | Claim uploads & extracts |
What Navigator does with these events
For each event, Navigator either:
- Auto-syncs and logs — if the Notification automation feature is on for your account, Navigator updates the customer record itself and leaves a system note. No manual task is created.
- Creates a task for review — if notification automation is off, your team sees a task tagged
ndis_api_notificationso someone can review and action the change manually.
See NDIS API — setup for the feature flags that control this behaviour.
When to dig deeper
If you want to understand a specific part of the NDIS integration, jump to:
- Setup — enabling the NDIS API for your account, PRODA device activation, and feature flags.
- Syncing funds & plans — how budgets and plans stay current with the NDIS.
- New & ended relationships — how plan manager changes reach your team.
- Claim uploads & extracts — the path from approved invoice to NDIS payment.