Quick Start

To integrate with MyndAuth:

1. Work with our support team to exchange credentials
2. Follow the Authentication section below to authenticate with our endpoint.
3. Build a FHIR Resource Bundle by following the section titled API Input.
4. Send the FHIR Resource Bundle to one of MyndAuth’s endpoints
5. A ClaimResponse Resource will be appended to the FHIR Resource Bundle that you sent to MyndAuth

MyndAuth requires two pieces of information for authentication.

• OAuth Flow
• provider_id

Both the OAuth flow and a provider_id must be exchanged before requests will be fulfilled. If you do not have either of the information, please reach out to Myndshft team.

Authentication is handled through an OAuth flow. Our support team will issue you client_id and client_secret which you will exchange for an access_token. The access_token MUST be sent when making requests to MyndAuth in a Authorization: Bearer {access_token} header.

Sample request to exchange client_id and client_secret values:

curl -X POST -H "Content-Type: application/x-www-form-urlencoded" \
"https://myndshft-sandbox.apigee.net/oauth/client_credential/accesstoken?grant_type=client_credentials" \
-d "client_id={client_id}&client_secret={client_secret}"

Sample response:

{
  "issued_at" : "",
  "application_name" : "",
  "scope" : "",
  "status" : "approved",
  "api_product_list" : "",
  "expires_in" : "3599", // seconds
  "developer.email" : "",
  "token_type" : "BearerToken",
  "client_id" : "",
  "access_token" : "AN ACCESS TOKEN",
  "organization_name" : "myndshft",
  "refresh_token_expires_in" : "0", // seconds
  "refresh_count" : "0"
}

The access_token is a short-lived value and will need to be renewed after expires_in seconds have elapsed.

In addition to the OAuth credentials our support team will issue you a provider_id value. This value MUST be sent with every request to MyndAuth in a header named X-Myndshft-Client-Id.

Example: X-Myndshft-Client-Id: 51e45ff2-5af3-45e6-915e-bd04257b87fc.