What Is API-Based NDIS Claiming and How Does It Work?

API-based NDIS claiming means submitting and managing payment requests through the NDIA’s application programming interfaces instead of the myplace provider portal’s manual upload or web interface. Registered providers connect either directly (applying for their own API access through the NDIA’s Digital Partnership Office) or indirectly (connecting through an existing approved software vendor or aggregator that already has API access). Once connected, providers can submit single or bulk payment requests, retrieve claim status, and manage service bookings programmatically — the same underlying rules that apply to portal transactions still apply to API transactions.

How does NDIS API access actually work?

The NDIA has developed APIs that allow controlled, secure access to specific NDIA data for approved entities supporting service delivery to participants. Through these APIs, an approved provider or software vendor can:

Submit and maintain payment requests against service bookings
Make single or multiple (bulk) payment requests
Retrieve information on submitted claims
Create, maintain, and delete service bookings
View and submit quotations
Share supporting documents with the NDIA

What is the difference between direct and indirect NDIS API integration?

	Direct integration	Indirect integration
Who applies	The provider applies directly to the NDIA Digital Partnership Office	The provider connects through an existing approved software vendor/aggregator
Technical burden	Provider (or their developers) builds against the NDIA’s API specifications and PRODA B2B authentication	Vendor has already built and maintains the integration
Approval process	Includes a cyber security assessment and application review by the DPO	Vendor’s aggregator status covers the connection; provider onboarding is typically faster
Best suited to	Providers with in-house development capability wanting a custom build	Most providers — using existing NDIS billing software that already holds API access

For most mid-market providers, indirect integration through an existing digital partner is the more practical path — it avoids the cyber assessment and ongoing API maintenance burden that direct integration carries.

How do NDIS software integrations protect participant information?

API access is granted specifically to protect the confidentiality, integrity, and availability of NDIS data — approved entities are responsible for that protection as a condition of access. Authentication runs through PRODA (Provider Digital Access), the same government identity system used for portal login, so API credentials are tied to a verified provider identity rather than a shared login. Software vendors offering indirect integration typically manage credential rotation and the secure channel to PRODA on the provider’s behalf, reducing the number of places sensitive participant and claim data is directly handled.

What are the practical benefits of API-based claiming over the portal?

Real-time status. Claim and service booking status can be retrieved on demand rather than checked manually in the portal.
Reduced double entry. Service bookings and claims created in a provider’s own billing or CRM system can sync automatically instead of being re-keyed into myplace.
Faster error visibility. API responses can surface claim issues immediately rather than waiting for a bulk file results download the next business day.
Scales with volume. High-volume providers submitting many claims per week benefit more from continuous API submission than from batching into periodic bulk uploads.