How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Salesforce Credential API

The Credential API from Salesforce — 6 operation(s) for credential.

Salesforce Credential API is one of 294 APIs that Salesforce publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Credential. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, a getting-started guide, and 1 JSON Schema.

This API exposes 13 operations across 6 paths, and defines 26 schemas. It is described by OpenAPI 3.1.0, at version v63.0.

Requests are made against a single base URL, https://{instance}.salesforce.com/services/data/v{version}/jobs.

13 operations 6 paths 26 schemas 3 DELETE3 GET1 PATCH3 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v63.0
Base URL
https://{instance}.salesforce.com/services/data
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Salesforce Credential API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — OAuth 2.0 Bearer token obtained from the Salesforce OAuth 2.0 token endpoint. Include this token in the Authorization header as "Bearer {accesstoken}".

Paths & Operations 13

Across 6 paths, the API surfaces 13 operations — 3 DELETE, 3 GET, 1 PATCH, 3 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Credential 13
GET
/data/v64.0/named-credentials/credential
Salesforce Get Credential
GetCredential 3 params → 200
POST
/data/v64.0/named-credentials/credential
Salesforce Create Credential
CreateCredential body → 201
PUT
/data/v64.0/named-credentials/credential
Salesforce Update Credential
UpdateCredential body → 200
DELETE
/data/v64.0/named-credentials/credential
Salesforce Delete Credential
DeleteCredential body → 200
POST
/data/v64.0/named-credentials/external-credentials
Salesforce Create External Credential
CreateExternalCredential body → 201
POST
/data/v64.0/named-credentials/named-credential-setup
Salesforce Create Named Credential
CreateNamedCredential body → 201
PUT
/data/v64.0/named-credentials/external-credentials/{DEVELOPER_NAME}
Salesforce Update External Credential
UpdateExternalCredential 1 param body → 200
DELETE
/data/v64.0/named-credentials/external-credentials/{DEVELOPER_NAME}
Salesforce Delete External Credential
DeleteExternalCredential 1 param → 204
GET
/data/v64.0/named-credentials/named-credential-setup/{DEVELOPER_NAME}
Salesforce Get Named Credential by Developer Name
GetNamedCredentialbyDeveloperName 1 param → 200
PUT
/data/v64.0/named-credentials/named-credential-setup/{DEVELOPER_NAME}
Salesforce Update Named Credential
UpdateNamedCredential 1 param body → 200
GET
/data/v64.0/tooling/sobjects/NamedCredential/{NAMED_CREDENTIAL_ID}
Salesforce Get Named Credential
Getnamedcredential 1 param → 200
DELETE
/data/v64.0/tooling/sobjects/NamedCredential/{NAMED_CREDENTIAL_ID}
Salesforce Delete Named Credential
Deletenamedcredential 1 param → 200
PATCH
/data/v64.0/tooling/sobjects/NamedCredential/{NAMED_CREDENTIAL_ID}
Salesforce Update Named Credential
Updatenamedcredential 1 param body → 200

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are SuccessfulUpdateNamedCredential (10 properties), SuccessfulCreateNamedCredential (10 properties), SuccessfulUpdateExternalCredential (10 properties), SuccessfulCreateExternalCredential (10 properties). Each schema is shown below with its type and property counts.

UpdateExternalCredentialRequest
object
4 properties 4 required
CustomHeader1
object
4 properties 4 required
Principal1
object
7 properties 7 required
Credentials
object
1 property 1 required
SuccessfulCreateExternalCredential
object
10 properties 10 required
UpdateNamedCredentialRequest
object
6 properties 6 required
DeleteCredentialRequest
object
3 properties 3 required
UpdatenamedcredentialRequest1
object
2 properties 2 required
CreateNamedCredentialRequest
object
7 properties 7 required
CreateCredentialRequest
object
5 properties 5 required
CreateExternalCredentialRequest
object
5 properties 5 required
Principal
object
3 properties 3 required
RelatedNamedCredential
object
4 properties 4 required
SuccessfulUpdateExternalCredential
object
10 properties 10 required
ExternalCredential1
object
4 properties 4 required
Metadata10
object
4 properties 4 required
CustomHeader
object
3 properties 3 required
SuccessfulCreateNamedCredential
object
10 properties 10 required
UpdateCredentialRequest
object
5 properties 5 required
SuccessfulGetCredential
object
7 properties 7 required
ExternalCredential2
object
1 property 1 required
SuccessfulGetNamedCredentialbyDeveloperName
object
10 properties 10 required
TestCredential
object
2 properties 2 required
successfulCreateCredential
object
6 properties 6 required
SuccessfulUpdateNamedCredential
object
10 properties 10 required
CalloutOptions
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

salesforce-credential-api-openapi.yml Raw ↑

Other APIs Salesforce publishes across the network.

Salesforce REST API
Salesforce SOAP API
Salesforce Bulk API
Salesforce Streaming API
Salesforce Metadata API
Salesforce Tooling API
Salesforce Connect API (Chatter)
Salesforce Analytics REST API
Salesforce Reports and Dashboards REST API
Salesforce Einstein Platform Services API
Salesforce Einstein Prediction Service API
Salesforce GraphQL API
Where this information came from

This is an independent, third-party profile of Salesforce Credential API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.