Setup & admin · 7 articles

API & integrations

How Navigator connects to external systems. The NDIS API (PRODA and PACE) carries the operational load — claims, fund sync, plan events. Dialpad syncs call data. These integrations run continuously once set up; this section covers what they do and how to troubleshoot.

At a glance

The NDIS API event pipeline

Data flows in and out of Navigator automatically — this is the typical path of an NDIS-driven change.
1
Event
NDIS sends Navigator a webhook (plan approved, budget updated, etc.).
2
Route
Paradox gateway verifies and routes to the right job.
3
Sync
Navigator fetches the latest data from PACE or PRODA.
4
Apply
Customer record is updated. System note left for audit.
5
Notify
Task created for your team if automation is off.

Jump in

Get started quickly

The most common starting points for this area.
Start here

NDIS API — overview

PRODA vs PACE, what each does, which events Navigator listens for.

Read the overview
Setup

NDIS API — setup

How an admin enables the NDIS integration for your account.

See setup
Daily

Syncing funds & plans

How funding and plans stay current with the NDIS — automatically and manually.

Understand syncing

Browse by topic

All articles

Organised the way your team thinks about this work.
NDIS API basics
2 articles
Data flowing in
2 articles
Data flowing out
1 article
When things go wrong
1 article
Other integrations
1 article

In a hurry?

Common questions

PRODA vs PACE matrix Sync a customer manually NDIS API feature flags When claims go wrong