The USI Developers Kit is provided by the USI Office and contains everything that is necessary to connect to USI web services. This includes test AUSkey and org codes, checksum algorithm, technical service contract, a web services presentation and other information.
Device AUSkeys are used for system to system web services and are installed on the server hosting a training organisation’s system. A Device AUSkey identifies a business rather than a person. This means users of a USI web service enabled Student Management Systems (SMSs) do not need their own individual AUSkey.
Device keys are used in two environments, Third Party Testing (3PT) and production.
The USI Office issues AUSkeys for the Third Party Testing.
The ABR manages all other AUSkeys for the production environment.
I want to know how to use web services to connect to the USI Registry System?
To establish web service functionality you will need the Technical Services Contract which includes details of the available USI web services. These services allow an authorised consumer to perform the following actions:
Create a USI record for an individual and receive an immediate response
Submit a batch of USI creation requests for processing
Retrieve the results of a previously submitted batch request
Verify a USI for an individual and receive an immediate response
Verify a batch of USIs and receive an immediate response.
What happens after I submit my USI Authentication Developers Kit (ADK) form
The USI Office will send you the USI Developers Kit which includes test AUSkey and org codes, checksum algorithm, technical service contract, a web services presentation and other useful web service testing information.