Customer Database website screenshot

Customer Database

Customer Database is the topic dedicated to APIs, schemas, vocabularies, and reference designs for the systems of record that store customer identity, profile, contact, preference, consent, and account data. A customer database underpins CRM, marketing automation, customer data platforms (CDPs), customer service, billing, and analytics use cases, and is increasingly expected to support API-first access, schema-on-write data quality, real-time eventing, GDPR/CCPA consent and erasure workflows, and identity resolution across web, mobile, and offline channels. This repository tracks the vendors, standards, and patterns that make customer data accessible, governed, and portable.

Customer Database is profiled on the APIs.io network. Tagged areas include Account, Consent, Contacts, CRM, and Customer Data.

The Customer Database catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Customer Database’s developer surface includes code examples and 23 more developer resources.

📡 Source on GitHub
15.2/100 emerging ▬ flat Agent 1/100 human only Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
0 APIs
AccountConsentContactsCRMCustomer DataCustomer Data PlatformCustomersDatabaseGDPRIdentityProfilesSchema

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Composite quality — 15.2/100 · emerging
Contract Quality 5.3 / 25
Developer Ergonomics 0.0 / 20
Access Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Contract Governance 4.1 / 12
Discoverability 5.7 / 10
Agent readiness — 1/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/customer-database: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Customer Database Context

52 classes · 22 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Customer Database API Rules

15 rules · 9 errors 6 warnings

SPECTRAL

JSON Schema 5

Standalone JSON Schema definitions for this provider's data models.

Customer Consent Record

13 properties

JSON SCHEMA

Customer Contact Point

10 properties

JSON SCHEMA

Customer Identity Link

10 properties

JSON SCHEMA

Customer Postal Address

10 properties

JSON SCHEMA

Customer Record

27 properties

JSON SCHEMA

JSON Structure 1

JSON Structure definitions describing this provider's data shapes.

Customer Database Structure

25 properties

JSON STRUCTURE

Examples 3

Example request and response payloads for these APIs.

Customer Consent Record Example

12 fields

EXAMPLE

Customer Identity Link Example

10 fields

EXAMPLE

Customer Record Example

22 fields

EXAMPLE

Resources

Documentation 7

Reference material describing how the API behaves

Schema.org Person
Schema.org Person
 Schema.org Vocabulary (JSON-LD)
Schema.org Vocabulary (JSON-LD)
 JSONSchema
JSONSchema
 JSONSchema
JSONSchema
 JSONSchema
JSONSchema
 JSONSchema
JSONSchema
 JSONSchema
JSONSchema

Scroll for all 7

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Vocabulary
Vocabulary
 DataModel
DataModel
 JSONStructure
JSONStructure
 JSONLD
JSONLD
 SpectralRules
SpectralRules

Build 3

SDKs, sample code, and the tooling you integrate with

Examples
Examples
 Examples
Examples
 Examples
Examples

Other 8

Properties that don't map to a standard resource type

Salesforce
Salesforce
 HubSpot
HubSpot
 Segment
Segment
 Customer.io
Customer.io
 Zendesk
Zendesk
 vCard 4.0 (RFC 6350)
vCard 4.0 (RFC 6350)
 SCIM 2.0
SCIM 2.0
 SCIM 2.0 Protocol (RFC 7644)
SCIM 2.0 Protocol (RFC 7644)

Scroll for all 8

Source (apis.yml)

apis.yml Raw ↑ 
aid: customer-database
name: Customer Database
description: Customer Database is the topic dedicated to APIs, schemas, vocabularies, and reference designs for the systems
  of record that store customer identity, profile, contact, preference, consent, and account data. A customer database underpins
  CRM, marketing automation, customer data platforms (CDPs), customer service, billing, and analytics use cases, and is increasingly
  expected to support API-first access, schema-on-write data quality, real-time eventing, GDPR/CCPA consent and erasure workflows,
  and identity resolution across web, mobile, and offline channels. This repository tracks the vendors, standards, and patterns
  that make customer data accessible, governed, and portable.
url: https://raw.githubusercontent.com/api-evangelist/customer-database/refs/heads/main/apis.yml
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/customer-database.png
tags:
- Account
- Consent
- Contacts
- CRM
- Customer Data
- Customer Data Platform
- Customers
- Database
- GDPR
- Identity
- Profiles
- Schema
created: '2024-01-15'
modified: '2026-08-13'
specificationVersion: '0.23'
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
common:
- type: Salesforce
  url: https://www.salesforce.com
- type: HubSpot
  url: https://www.hubspot.com
- type: Segment
  url: https://segment.com
- type: Customer.io
  url: https://customer.io
- type: Zendesk
  url: https://www.zendesk.com
- type: Schema.org Person
  url: https://schema.org/Person
- type: vCard 4.0 (RFC 6350)
  url: https://datatracker.ietf.org/doc/html/rfc6350
- type: SCIM 2.0
  url: https://datatracker.ietf.org/doc/html/rfc7643
- type: SCIM 2.0 Protocol (RFC 7644)
  url: https://datatracker.ietf.org/doc/html/rfc7644
- type: Schema.org Vocabulary (JSON-LD)
  url: https://schema.org/version/latest/schemaorg-current-https.jsonld
- type: LLMsTxt
  url: llms/customer-database-llms.txt
- type: Vocabulary
  url: vocabulary/customer-database-vocabulary.yml
- type: DataModel
  url: data-model/customer-database-data-model.yml
- type: JSONSchema
  url: json-schema/customer-record.json
- type: JSONSchema
  url: json-schema/customer-contact-point.json
- type: JSONSchema
  url: json-schema/customer-postal-address.json
- type: JSONSchema
  url: json-schema/customer-consent-record.json
- type: JSONSchema
  url: json-schema/customer-identity-link.json
- type: JSONStructure
  url: json-structure/customer-database-structure.json
- type: JSONLD
  url: json-ld/customer-database-context.jsonld
- type: SpectralRules
  url: rules/customer-database-jsonschema-spectral-rules.yml
- type: Examples
  url: examples/customer-record-example.json
- type: Examples
  url: examples/customer-consent-record-example.json
- type: Examples
  url: examples/customer-identity-link-example.json
x-enrichment:
  date: '2026-08-13'
  status: minimal
  artifacts_added: 14
  pass: local-v1
x-coverage:
  state: none
  reason: not-a-software-company
  detail: 'Customer Database is an API Evangelist topic reference, not a company — apis.yml declares apis: [] and the profile
    exists to point at the vendors and open standards in the customer-data space, so there is no vendor, no host, and no API
    of its own to document. repair-api-bases.py returned "missing" and probe-domain-security.py returned "no-hosts" because
    no API entry names a base URL. The 14 artifacts added this pass are neutral, standards-grounded reference material (a
    vocabulary, a SCIM/vCard/Schema.org field crosswalk, five JSON Schemas, a JSON Structure, a JSON-LD context, a Spectral
    ruleset, examples and an llms.txt), not a vendor surface. See the individual vendor repositories — salesforce, hubspot,
    segment, customer-io, zendesk — for real APIs.'
  evidence:
  - url: https://raw.githubusercontent.com/api-evangelist/customer-database/refs/heads/main/apis.yml
    status: 200
  - url: https://schema.org/version/latest/schemaorg-current-https.jsonld
    status: 200
  - url: https://www.rfc-editor.org/rfc/rfc7643.txt
    status: 200
  checked: '2026-08-13'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/customer-database"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/customer-database/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/customer-database/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.