Create a Named Credential for Scheduling

Named Credential for an External Scheduling System

For an external scheduling system, Salesforce handles the authentication. You can skip setting up the remote site settings that are usually required for REST calls to external sites.

A named credential specifies the base URL for REST endpoints and any required authentication parameters in one definition, which simplifies REST call setup. If you register the base URL in your org’s remote site settings instead, you must handle the authentication yourself. For example, for an Apex callout, your code must handle authentication, which can be less secure and especially complicated for OAuth implementations.

When you create the named credential, instead of clicking New, select New Legacy from the dropdown menu next to the New button.

• An example URL value that references the HAPI FHIR open-source system is https://hapi.fhir.org/baseR4.
• For more details about the Health Cloud named credential, see Operations. For detailed general steps to create a legacy named credential, see Define a Legacy Named Credential.

Named Credential for Salesforce Scheduler

Salesforce Scheduler requires a named credential but doesn't use it. The URL that you specify must be properly formatted, but the value doesn't matter. If you created a legacy named credential for an external scheduling system, you can use the same one for Salesforce Scheduler. If you create a named credential only for Salesforce Scheduler, you can use the URL https://www.example.com. When you create the named credential, instead of clicking New, select New Legacy from the dropdown menu next to the New button.