API v1 Setting up a new Answering Service company

Ensure the Answering Service Company has the latest API document (attached).

On the CC site, have "Answering Service" practice created and enabled.

Create the user account for the API service to use. Have the "COMPANY" field entered as the actual name of the Answering Service.

This name will generate a doctor in the "Answering Service" on their first attempt to use the API.

Have the Answering Service execute a list of doctors request (to create the A/S doctor profile on first attempt).

If "Answering Service" practice has blank doctor names, sometimes a bunch of these would exists. Please disable all of them. These were created as the API user did not have a "COMPANY" name in the user profile.
Important notes regarding API version 1 and version 2.
API v1 = GET, Submit a ticket, check which MD is on call for a practice, get list of doctors for a practice, send a secure message to a doctor. Supports Proxy. (will not get further updates).
API v2 = POST. same features as v1, get status of ticket, return results of a triage, token authentication. Complaint Analyzer*. Does not support Proxy.(and many new features* going forward, a few in dev stages now).