API Build & Test

We have provided the following testing Infrastructure to support you in the journey.

 

Sandbox Environment

Compliance Environment

Use

A chance to learn.

This has dummy data and is not linked to ACC’s back-end systems so use this to play and learn. 

 

Finishing touches. The compliance environment mimics the production experience including using real data.   As a minimum reuse the ACC published scenarios.  When you are ready, sign the terms & conditions pertaining to the Compliance Environment etc; this will provide you with access to this environment.

Further details on the compliance process following this table. 

Getting Access

You will need to register then request access to the environments.  Access requirements are covered in the “Get Started” guide for APIs, including any legals.

API Authentication and Access

All API requests need an API key. We'll issue your own sandbox API key once you register an app.

Our one exception: The 'test' API key for HCSS is 6HoTt9GsONTE6eli2LGZVa0vVYfJa1VN. You can also find it next to the API key field in Our APIs/specific API/endpoint description.

All API requests need an API key. We’ll issue your own compliance API key once you sign the necessary terms & conditions.

You will also need a valid Developer Health Secure Digital Certificate x.509 to submit some requests in compliance environments..

The Health Secure Digital Certificate is the same certificate Providers use to submit payloads using the current online service for testing. You may already have requested for Developer Digital Certificate as part of the registration process.  If not, you can get one by Contacting Us and providing the following details:

1.     Complete the Name, Email

2.     Select ‘Request Access’ in the 'What are you contacting us about' field.

3.     Select “Build” and “Test” for “API”

4.     Note that you need a Developer Digital Certificate for testing in the “Message”

Guides

Support material for APIs consists of:

1.     Swagger Specification;

2.     Tips and tricks e.g. Guide to building User Interfaces

Play

Apigee SmartDocs feature to fire up APIs at will and see what happens!

 

Test Scenarios

Use your scenarios & ACC published test scenarios per API.

If you are applying for to release you API Apps into Production, ACC requires evidence of testing and results for the published test scenarios at a minimum.  The “Release to Production” process is covered in “Get Started” guide.

Test Data

Fabricated data used in responses.    Please don’t send notes relating to real clients, or their real ACC45 numbers or ACC claim numbers in sandpit environment. Please use dummy data (e.g. Jane Doe as client name, 4/7/1776 or 6/2/1840 or similar famous days as birthday ##12345 as ACC45 etc.).     

For Provider-related services: Claim numbers will need to be allocated to each developer as there is a set number range that is available to submit into the Compliance environment. May need provider and vendor..

These numbers can be requested from our <support team> team through the contact us form

Suggested scenarios to test

Our scenarios to test against for claims, claim queries and medical certificate and/or invoices, invoice queries and payment status should be completed and copies of the payload and response data should be kept as they will need to be passed to the digital operations team for verification purposes. Some tests will require screenshots of your system or the printed output from your system to be given to ACC to verify as well. There may be further testing and requirements which will be at ACC's discretion.