---
schema_version: "1"
id: e3bdbb8dc1ab01953f01f20203002d1aeceee20064b4d306f87b10cfb5e34566
title: Create a Named Credential for Scheduling
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/create_a_named_credential.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.create_a_named_credential.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 32d4204bfc07b29305e4c7b0e7152e6fd45b672c0f2cd61e338a62099da6211a
description: Create a named credential for your back-end scheduling system. You can use the same named credential for both an external scheduling system and Salesforce Scheduler.
products:
  - Health
release: "264"
---
# Create a Named Credential for Scheduling

Create a named credential for your back-end scheduling system. You can use the same named credential for both an external scheduling system and Salesforce Scheduler.

## 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](https://developer.salesforce.com/docs/atlas.en-us.health_cloud_object_reference.meta/health_cloud_object_reference/healthcare_appointment_booking_operations.htm). For detailed general steps to create a legacy named credential, see [Define a Legacy Named Credential](https://help.salesforce.com/s/articleView?id=xcloud.named_credentials_define.htm&type=5&language=en_US).

## 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.

#### See Also

- [About Named Credentials](https://help.salesforce.com/s/articleView?id=xcloud.named_credentials_about.htm&type=5&language=en_US)