Recuro Health APIs use OpenID Connect (OIDC) and OAuth 2.0 protocol for authentication and authorization. Recuro Health supports scenarios for server-side, mobile, desktop, client-side, server, and device applications. Only client authorization flows are available by default, so let your Recuro Health Account Manager know if you are interested in access to additional flows.

Endpoint

Single Sign On (SSO)

If you're looking for information on Single Sign On capabilities, start with our SSO Guide.

Authorization

Depending on your specific needs, there are a few different flows you can use to authorize your apps and users with the Recuro Health API.

Client Credentials Flow (Service)

The service client credentials flow is used when your app is authenticating itself directly.

Client Credentials Flow (User)

The user client credentials flow is used when your app is authenticating itself on behalf of one of your users.

Integration Methods

The Authentication API is accessible by referencing the REST API directly or by using a Recuro Health SDK. To get started, choose an option below.