Intended to secure and simplify authenticated API callouts to external systems, a named
credential specifies the URL of a callout endpoint and its required authentication parameters in
one definition. To streamline your Apex code and simplify the setup of authenticated callouts,
specify a named credential as the callout endpoint.
Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning
Experience
Available in: all editions
Important In Winter ’23, Salesforce
introduced an improved named credential that’s extensible, customizable, and more
secure. We strongly recommend that you use this preferred credential instead of
legacy named credentials, which are no longer updated or enhanced. For information
on extensible, customizable named credentials, see Named
Credentials Schema.
Get Started with Named Credentials Understand the basics of named credentials, including the named credential schema and the authentication protocols that Salesforce supports.
Named Credential Example Configurations Explore scenarios for configuring named credentials to make callouts to various external systems. The examples cover the entire named credential configuration for different authentication protocols and principal types.
Create Named Credentials and External Credentials To simplify the setup of authenticated callouts, create an external credential to specify an authentication protocol and then specify a named credential as the callout endpoint. Add custom headers to cover more use cases and security requirements. Use a permission set or profile to grant access so that users can make authenticated callouts. You can create and configure named credentials programmatically or through the Salesforce UI.
Resources for Named Credentials Learn about considerations, troubleshooting tips, and more so that named credentials work the way you intend.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.