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

LiveRamp Credential Sources API

The Credential Sources API from LiveRamp — 3 operation(s) for credential sources.

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

Tagged areas include Credential Sources. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a changelog.

This API exposes 3 operations across 3 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version v1.0.0.

Requests are made against a single base URL, https://api.habu.com/v1/.

3 operations 3 paths 5 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1.0.0
Base URL
https://api.liveramp.com/activation
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

LiveRamp Credential Sources API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (application) using the clientCredentials flow. By default, every request must be authenticated.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

Credential Sources 3
GET
/credential-sources
Fetch a list of all Credential Sources
getAllCredentialSources → 200400401403404500
GET
/credential-sources/{credentialSourceId}
Fetch a Credential Source by ID
getCredentialSourceById 1 param → 200400401403404500
GET
/credential-sources/credential-name/{name}
Fetch a Credential Source by Name
getCredentialSourceByName 1 param → 200400401403404500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are CredentialConfig (5 properties), CredentialConfigListValue (4 properties), CredentialSource (4 properties), ReturnObject (2 properties). Each schema is shown below with its type and property counts.

CredentialSource
object
4 properties
CredentialSources
array
CredentialConfigListValue
object
4 properties
CredentialConfig
object
5 properties
ReturnObject
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

liveramp-credential-sources-api-openapi.yml Raw ↑

Other APIs LiveRamp publishes across the network.

LiveRamp Authenticated Traffic Solution (ATS) API
LiveRamp AbiliTec API
LiveRamp RampID API
LiveRamp Data Marketplace Buyer API
LiveRamp Data Seller API
LiveRamp Safe Haven Job Management API
LiveRamp Data Pipeline Visibility API (Beta)
LiveRamp Sidecar
LiveRamp Billable Configs API
LiveRamp Cleanroom API
LiveRamp Cleanroom Datasets API
LiveRamp Cleanroom Destinations API
Where this information came from

This is an independent, third-party profile of LiveRamp Credential Sources 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.