Specifications & Guides
Sandbox API Specification
The Sandbox API Specification below details how to access and use the Sandbox (Test) environment:
Common API Specification
The Common API Specification describes functions, components, and validation common to all the APIs, in particular:
Lists the APIs, source documents, and common terminology
Outlines the common API Processing for all endpoints
Describes common data types and error messages
Specifies common data inputs, formats and validations for submitting a request and queries applying to 2 or more APIs, respectively
Describes translation of Read (or diagnosis) codes between ACC’s system and SNOMED codes
We highly recommend reading the Common API Specification before any development; see below.
We recommend reading the ACC Design Primitives document below for insight into how ACC has put its APIs together.
Individual API Specifications
We recommend reading the applicable individual API specification below, in parallel with working with the swagger.
184 KB - Outlines ACC's Design Primitives transport, URI design, standards, representation & more.
620 KB - Specifies the API for adding a new diagnosis to a submitted claim, or changing / deleting an existing diagnosis.
645 KB - Specifies the API for submitting a claim request for processing by the eChannel gateway which may be passed to EOS.
626 KB - Describes functions, components, and validation common to all the APIs.
492 KB - Specifies hot to use the HCSS API accept data for new reporting requirements.
319 KB - Inbound Documents API Specification
356 KB - Specifies the API for submitting a schedule of invoices,
395 KB - Specifies the API for submitting a medical certificate request for processing by the eGateway.
724 KB - Specifies ways for a health provider to find information about claims that have been submitted to eChannel.
758 KB - Specifies ways for a health provider to find information about schedules of invoices submitted to the eGateway.
275 KB - Spec on how to use the ACC virtual test environment.