The NDIA is developing a Digital Partnership Program (DPP), which will manage controlled and secure access to some of the NDIA’s data and systems. Access will be managed via Application Programming Interfaces (APIs). These APIs are being created so providers and software developers can create new tools, applications and digital marketplaces to improve how participants, providers and the NDIA all connect and work together.
The NDIA is providing access to Application Programming Interfaces (APIs) to allow connections between registered providers and some NDIA systems and data. These APIs will be managed and improved on by the NDIA Digital Partnership Office (DPO).
Currently APIs are available for registered providers only for the purpose of automating transactions they would usually complete in the myplace Provider Portal.
More work is being done to release more APIs and allow other businesses to start accessing NDIA APIs.
How to start using NDIA APIs
1. Register for Development Access
- Download and complete:
- NDIA Digital Providers Questionnaire (PDF 518KB)
- NDIA Digital Providers Terms and Conditions (PDF 27KB)
- Obtain a current (within four weeks of sending) company extract for your company. This can be purchased for a small fee on the ASIC website. The date on the extract should be no earlier than four weeks prior to the date you post these documents to NDIA.
- Email responses to DPO@ndis.gov.au.
- Post hard copies of the completed documents and company extract to:
API Onboarding
NDIA Digital Partnership Office
GPO Box 700
CANBERRA ACT 2601
Please note original hard copies of your documents must be received before access can be granted. - The DPO will review your application and let you know the outcome.
- If your application is successful, we will send you a technical pack with:
- Onboarding Guide
- NDIA PRODA step-by-step guide API Connect
- PRODA B2B Software Developers Guide.
- Register for a PRODA test account by following the instructions in the technical pack.
- Activate your account in the vendor developer portal using the link that will be emailed to you.
- You can then view the API specifications in the vendor developer portal.
2. Access to NDIA Production APIs
To gain access to our APIs in the production environment, you will need to:
- Finish developing the software you want to publish.
- Email the API support team to let them know you are ready to test. They will send you a test plan test data and test results template.
- Return your completed test results for the API support team to review.
- Once successful, we will let you know and start the process to grant production access, including whitelisting and PRODA client ID details.
- Complete PRODA production authentication, and you will have production access.
If you have any questions about the APIs, email DPO@ndis.gov.au.
Availiable APIs
All APIs are subject to the same rules that apply to myplace provider portal transactions. Refer to the provider portal guides for more information.
Payment Requests API
Submit and maintain payment requests against service bookings via APIs. You can make requests for single or multiple payments and retrieve information on submitted requests.
| API description | Use |
|---|---|
| Payment Request Creation Single | Submit a single payment request for one service booking |
| Payment Request Creation Batch | Submit a set of payment requests for multiple service bookings and participants |
| Payment Request List All | Retrieve a list of all payment requests made by the provider |
| Payment Request List Specific | Retrieve a single payment request made by the provider |
Service Booking API
Create, maintain and delete service bookings.
| API Description | Use |
|---|---|
| Service Booking Creation | Places a service booking against a participant’s funded supports. This allows the provider to make a service booking for a support category or support item. |
| Service Booking Update Quantity and Amount | Updates the current quantity and allocated amount of an existing service booking |
| Service Booking Extend End Date | Extends the ending date of an existing service booking |
| Service Booking Reduce End Date | Reduces the ending date of an existing service booking |
| Service Booking Update Status | Updates the status of an existing Service Booking in the Participants plan. |
| Service Booking List All | Retrieves a list of all the provider’s service bookings |
| Service Booking List Specific | Retrieves a specific service booking assigned to the provider |
| Service Booking Delete | Deletes a specific service booking assigned to the provider |
Quotations API
View and submit new quotations.
| API Description | Use |
|---|---|
| Quotation List All | Retrieves a summary of all quotations for the provider along with current status on each |
| Quotation Response | Responds to a specific request for a quote from NDIA |
Notifications API
View and manage notifications that you have signed up for, including:
- Quotation response required
- Service booking awaiting participant approval
- Service booking awaiting provider approval.
| API Description | Use |
|---|---|
| Notification List All | Retrieves a list of all the notifications that a provider has subscribed to receive |
| Notification Subscribe | Enables the provider to subscribe to a type of notification |
| Notification Unsubscribe | Enables the provider to unsubscribe from a previously subscribed type of notification |
Product Catalogue API
Looks up a specific product name.
| API Name | Use |
|---|---|
| Product Catalogue View | Retrieves NDIA’s Product Catalogue details |
File Upload API
Share a supporting document with NDIA.
| API Name | Use |
|---|---|
| Upload File | Uploads a file as a supporting document |
Reference Data API
Retrieve all information needed to use each existing API.
| API Name | Use |
|---|---|
| Reference Data All | Retrieves a list of all the required datasets and parameters for the developer to know |
| Reference Data Attribute | Retrieves values for a specific attribute that needs to be passed into other APIs |
| Reference Data Sub-attribute | Retrieves values for a specific sub attribute data that needs to be passed into other APIs |
Real Time Claims
The NDIA is investigating the development and implementation of a Real Time Claims and Direct Payment solution that will provide simple, consistent, automated claims and payment processes. The intent is to dramatically reduce the effort, time and cost associated with making claims, receiving payments and resolving issues under the current payments processes.
The Request for Information (RFI) or Approach to Market (APM) presents a number of use cases and includes a rage of technical requirements.
DIA has sort clarity on a number of language points contained within the document most notably, page 13…
“eliminate the need for Plan managers and Participants to be financial intermediaries to reduce the time gap between Providers providing a support and receiving payment.”
DIA has been assured that the intent of this is not to reflect a desire to remove the functions of Plan Management, rather this statement is in reference to Participants in some cases needing to expend money their own money and then claim for reimbursement. The NDIA acknowledge that this could be misinterpreted and stress the intent is not to remove the function of Plan Management.
On the 5th of June the NDIA released REAL TIME CLAIMS APPROACH TO MARKET ADDENDUM NO.2 on the AusTender website. This addendum contains a full list of Questions and response.
Question 24
Given the real-time nature of the proposed model, are NDIA looking to remove the middle plan manager level or will this requirement remain in place?Answer 24
There is no intent to remove the function of registered provider plan managers from the NDIS system with the introduction of real time claims. The automated process flow for claims initiated by the real time claims solution will change, however, and the role that plan managers currently play in the processing of those claims may also change.
The NDIA also points to the features section which highlights the use of Plan Management including:
F1.12: Provides real time support to the Participant or their nominee, the Plan Manager, and the Provider to address issues that occur at the POS and when claims are rejected.
F3.1: Capable of receiving the outcome of the claims assessment at POS in real time and notifying the Provider, Participant, nominee and/or Plan manager of that outcome.
F4.1: Allows claims and payments to be made directly from and to Providers for self and Plan Managed Participants without the Participant needing to fund the support themselves. This is to remove the need for reimbursements.
F5.1: Enables alerts and notifications in real time to Participants, nominees, Providers and Plan managers to inform claim and payment events (e.g. claim lodged, claim approved, claim rejected, payment made).
F5.3: Enables ad hoc alerts and notifications to be sent to Participants, nominees, Providers and Plan managers at the discretion of the NDIA.
F5.4: Enables alerts and notifications to be sent to Participants, nominees, Providers and Plan managers individually or in bulk.
F5.5: Enables alerts and notifications to be sent to Participants, nominees, Providers and Plan managers using their preferred method of choice (e.g. sms, email, push notification)
F6.4: Ability to provide regular, ad hoc and on demand reporting to Participants, nominees, Providers, Plan managers and the NDIA
Submissions close 12th June 2020 at 4PM (ACT time).
DIA encourages any members who have been developing technology to consider responding.