Eligibility API
| No. | Environment | Item | Value | Description |
|---|---|---|---|---|
| 1.1 | Staging (UAT) | Base URL | https://stage-members.mdlivetechnology.com/services/ |
|
| 1.2 | Production | Base URL | https://members.mdlive.com/services/ |
|
| 2.1 | Required for All | HTTP Request Header: Content-Type |
application/json |
|
| 2.2 | Required for All | HTTP Request Header: Authorization |
application/json |
Each API user is assigned an API Key and Secret pair that will grant access to the API. MDLIVE uses HTTP BASIC Authentication where the key and secret are used as the username and password respectively. This needs to be sent as part of the Header in the API request. Example: Authorization: Basic <Base64 encoding of "key:secret"> |
| 2.3 | Required for All | HTTP Request Header: RemoteUserId |
application/json |
Use this header to specify which user triggered this API call. This is required for auditing purposes and requests without this header would be declined. This can be your organization name. |
| No. | Item | Description |
|---|---|---|
| 1 | Storing MDLIVE Member IDs | Client is responsible for storing MDLIVE Member ID (or unique identifier) in their system. When an API call to add a member is passed to MDLIVE, MDLIVE will respond back with a MDLIVE Member ID that is associated to that member / person record. This MDLIVE Member ID must be used when making any modifications or deleting the member. |
| 2 | MDLIVE does not deny service | MDLIVE will not deny service to a member that calls for a consult. If the member is not in our system and provides the group / employer name, our call center will add them into our system so that they can proceed with their consult. At the time the member is added into our system, MDLIVE will generate a new MDLIVE Member ID. |