NICE

NICE provides a comprehensive Customer Experience (CX) AI platform that orchestrates human and AI agents, automates service, and empowers workforces. Their solutions span enterprise CX AI, integrations, cloud architecture, and agent workspaces, delivering scalable intelligent experiences across industries.

NICE is listed with 11 APIs on the APIs.io network, including Channels API, Contacts API, Incontactapi API, and 8 more. Tagged areas include Company, Customer Experience, Artificial Intelligence, Cloud, and Integration.

The NICE catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

NICE’s developer surface includes authentication, documentation, getting-started guide, engineering blog, pricing, support, and 18 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

41.6/100 developing ▼ -8.6 Agent 24/100 agent aware Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaidSelf serve

11 APIs

Company Customer Experience Artificial Intelligence Cloud Integration

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 41.6/100 · developing

Contract Quality 6.1 / 19

Developer Ergonomics 4.7 / 15

Access Clarity 10.1 / 15

Operational Transparency 1.8 / 10

Contract Governance 3.2 / 9

Discoverability 5.2 / 8

Regulatory Posture 3.2 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/nice/"><img src="https://apis.io/badge/nice/card.svg" alt="NICE on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 32.4 — up to +16.9 composite points
Developer Ergonomics scores 31.0 — up to +13.8 composite points
Operational Transparency scores 18.4 — up to +10.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/nice/apis.yml: open an issue on github.com/api-evangelist/nice to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 11

Individual APIs this provider publishes, each with its own machine-readable definition.

NICE Contact Center API

API for NICE Contact Center platform, providing endpoints for contact management, reporting, and integration.

NICE Channels API

The Channels API from NICE — 1 operation(s) for channels.

NICE Contacts API

The Contacts API from NICE — 1 operation(s) for contacts.

NICE Incontactapi API

The Incontactapi API from NICE — 3 operation(s) for incontactapi.

NICE Perform Action API

The Perform Action API from NICE — 1 operation(s) for perform action.

NICE Result API

The Result API from NICE — 1 operation(s) for result.

NICE Segments API

The Segments API from NICE — 1 operation(s) for segments.

NICE Status API

The Status API from NICE — 1 operation(s) for status.

NICE User Management API

The User Management API from NICE — 14 operation(s) for user management.

NICE Voice Print Status API

The Voice Print Status API from NICE — 1 operation(s) for voice print status.

NICE .well Known API

The .well Known API from NICE — 1 operation(s) for .well known.

Scroll for all 11

NICE API pricing

Prices published by NICE, read 2026-10-28 from www.nice.com/pricing.

Plan	Price
Omnichannel Suite	$110
Essential Suite	$135
Core Suite	$169
Complete Suite	$209
Ultimate Suite	$249/ $0.25
The Ultimate Banking Experience	$249/ $0.25
The Ultimate Insurance Experience	$249/ $0.25
The Ultimate Healthcare Experience	$249/ $0.25

All 10 plans, limits and sources →

Billed by: agent per month / per session · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Nice Plans Pricing

10 plans

PLANS

Nice Price Estimates

0 plans

PLANS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

NICE

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Nice Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Nice Webhooks

ASYNCAPI

Semantic Vocabularies 1

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

Nice Context

5 classes · 20 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

NICE API Rules

9 rules · 7 errors 1 warnings 1 info

SPECTRAL

JSON Schema 5

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

GetStatusRequestidResponse

2 properties

JSON SCHEMA

GetWellKnownOpenidConfigurationResponse

16 properties

JSON SCHEMA

PostChannelsRequest

1 properties

JSON SCHEMA

PostContactsResponse

1 properties

JSON SCHEMA

PostSegmentsResponse

1 properties

JSON SCHEMA

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Nice Authentication

1 scheme

SECURITY

Nice Domain Security

TLSv1.3 · DMARC

SECURITY

Nice Trust Center

SOC 2, ISO 27001, PCI DSS, FedRAMP

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

Webhooks

DataModel

Conformance

Access & Security 5

Authentication, authorization, and security posture

Compliance

Authentication

SecurityTxt

TrustCenter

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans

TermsOfService

PrivacyPolicy

Pricing

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Hosts

Hosts

Source (apis.yml)

aid: nice
name: NICE
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Paid · Self-serve signup
  confidence: medium
  probe_state: unreadable
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://resources.nice.com/wp-content/uploads/2025/08/NiCE-logo.jpg
description: NICE provides a comprehensive Customer Experience (CX) AI platform that orchestrates human and AI agents, automates
  service, and empowers workforces. Their solutions span enterprise CX AI, integrations, cloud architecture, and agent workspaces,
  delivering scalable intelligent experiences across industries.
url: https://raw.githubusercontent.com/api-evangelist/nice/refs/heads/main/apis.yml
x-type: company
x-source: harvest:tag-qc
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-14 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-14'
modified: '2026-10-14'
tags:
- Company
- Customer Experience
- Artificial Intelligence
- Cloud
- Integration
tags_raw:
- Company
- CustomerExperience
- AI
- Cloud
- Integration
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/nice-plans-pricing.yml
- type: Spectral
  url: rules/nice-rules.yml
- type: JSONLD
  url: json-ld/nice-context.jsonld
- type: Vocabulary
  url: vocabulary/nice-vocabulary.yml
- type: Webhooks
  url: asyncapi/nice-webhooks.yml
- type: DataModel
  url: data-model/nice-data-model.yml
- type: Compliance
  url: https://www.nice.com/company/trust-center
- type: Authentication
  url: authentication/nice-authentication.yml
- type: Conformance
  url: conformance/nice-conformance.yml
- type: LLMsTxt
  url: llms/nice-llms.txt
- type: SecurityTxt
  url: well-known/nice-help-security.txt
- type: WellKnown
  url: well-known/nice-well-known.yml
- type: Hosts
  url: hosts/nice-hosts.yml
- type: TermsOfService
  url: https://www.nice.com/company/legal/terms-of-use
- type: PrivacyPolicy
  url: https://www.nice.com/company/legal/privacy-policy
- type: TrustCenter
  url: security/nice-trust-center.yml
- type: DomainSecurity
  url: security/nice-domain-security.yml
- type: Website
  url: https://www.nice.com
- type: DeveloperPortal
  url: https://developer.niceincontact.com/
- type: Documentation
  url: https://developer.niceincontact.com/Documentation
- type: GettingStarted
  url: https://developer.niceincontact.com/Documentation/GettingStarted
- type: Blog
  url: https://www.nice.com/blog
- type: Pricing
  url: https://www.nice.com/pricing
- type: Support
  url: https://www.nice.com/services/customer-support
apis:
- name: NICE Contact Center API
  description: API for NICE Contact Center platform, providing endpoints for contact management, reporting, and integration.
  humanURL: https://developer.niceincontact.com/Documentation/GettingStarted
  baseURL: null
  aid: nice:nice-contact-center-api
- aid: nice:nice-channels-api
  name: NICE Channels API
  description: The Channels API from NICE — 1 operation(s) for channels.
  humanURL: https://developer.niceincontact.com/Documentation/GettingStarted
  baseURL: https://api-do72.dev.nice-incontact.com
  tags:
  - Channels
  properties:
  - type: OpenAPI
    url: openapi/nice-channels-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nice-get-well-known-openid-configuration-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-get-status-requestid-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-channels-request-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-segments-response-schema.json
- aid: nice:nice-contacts-api
  name: NICE Contacts API
  description: The Contacts API from NICE — 1 operation(s) for contacts.
  humanURL: https://developer.niceincontact.com/Documentation/GettingStarted
  baseURL: https://api-do72.dev.nice-incontact.com
  tags:
  - Contacts
  properties:
  - type: OpenAPI
    url: openapi/nice-contacts-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nice-get-well-known-openid-configuration-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-get-status-requestid-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-channels-request-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-segments-response-schema.json
- aid: nice:nice-incontactapi-api
  name: NICE Incontactapi API
  description: The Incontactapi API from NICE — 3 operation(s) for incontactapi.
  humanURL: https://developer.niceincontact.com/Documentation/GettingStarted
  baseURL: https://api-do72.dev.nice-incontact.com
  tags:
  - Incontactapi
  properties:
  - type: OpenAPI
    url: openapi/nice-incontactapi-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nice-get-well-known-openid-configuration-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-get-status-requestid-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-channels-request-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-segments-response-schema.json
- aid: nice:nice-perform-action-api
  name: NICE Perform Action API
  description: The Perform Action API from NICE — 1 operation(s) for perform action.
  humanURL: https://developer.niceincontact.com/Documentation/GettingStarted
  baseURL: https://api-do72.dev.nice-incontact.com
  tags:
  - Perform Action
  properties:
  - type: OpenAPI
    url: openapi/nice-perform-action-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nice-get-well-known-openid-configuration-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-get-status-requestid-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-channels-request-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-segments-response-schema.json
- aid: nice:nice-result-api
  name: NICE Result API
  description: The Result API from NICE — 1 operation(s) for result.
  humanURL: https://developer.niceincontact.com/Documentation/GettingStarted
  baseURL: https://api-do72.dev.nice-incontact.com
  tags:
  - Result
  properties:
  - type: OpenAPI
    url: openapi/nice-result-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nice-get-well-known-openid-configuration-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-get-status-requestid-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-channels-request-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-segments-response-schema.json
- aid: nice:nice-segments-api
  name: NICE Segments API
  description: The Segments API from NICE — 1 operation(s) for segments.
  humanURL: https://developer.niceincontact.com/Documentation/GettingStarted
  baseURL: https://api-do72.dev.nice-incontact.com
  tags:
  - Segments
  properties:
  - type: OpenAPI
    url: openapi/nice-segments-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nice-get-well-known-openid-configuration-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-get-status-requestid-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-channels-request-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-segments-response-schema.json
- aid: nice:nice-status-api
  name: NICE Status API
  description: The Status API from NICE — 1 operation(s) for status.
  humanURL: https://developer.niceincontact.com/Documentation/GettingStarted
  baseURL: https://api-do72.dev.nice-incontact.com
  tags:
  - Status
  properties:
  - type: OpenAPI
    url: openapi/nice-status-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nice-get-well-known-openid-configuration-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-get-status-requestid-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-channels-request-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-segments-response-schema.json
- aid: nice:nice-user-management-api
  name: NICE User Management API
  description: The User Management API from NICE — 14 operation(s) for user management.
  humanURL: https://developer.niceincontact.com/Documentation/GettingStarted
  baseURL: https://api-do72.dev.nice-incontact.com
  tags:
  - User Management
  properties:
  - type: OpenAPI
    url: openapi/nice-user-management-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nice-get-well-known-openid-configuration-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-get-status-requestid-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-channels-request-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-segments-response-schema.json
- aid: nice:nice-voice-print-status-api
  name: NICE Voice Print Status API
  description: The Voice Print Status API from NICE — 1 operation(s) for voice print status.
  humanURL: https://developer.niceincontact.com/Documentation/GettingStarted
  baseURL: https://api-do72.dev.nice-incontact.com
  tags:
  - Voice Print Status
  properties:
  - type: OpenAPI
    url: openapi/nice-voice-print-status-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nice-get-well-known-openid-configuration-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-get-status-requestid-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-channels-request-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-segments-response-schema.json
- aid: nice:nice-well-known-api
  name: NICE .well Known API
  description: The .well Known API from NICE — 1 operation(s) for .well known.
  humanURL: https://developer.niceincontact.com/Documentation/GettingStarted
  baseURL: https://api-do72.dev.nice-incontact.com
  tags:
  - .well Known
  properties:
  - type: OpenAPI
    url: openapi/nice-well-known-api-openapi.yml
  - type: JSONSchema
    url: json-schema/nice-get-well-known-openid-configuration-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-get-status-requestid-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-channels-request-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-contacts-response-schema.json
  - type: JSONSchema
    url: json-schema/nice-post-segments-response-schema.json
x-coverage:
  state: unreadable
  reason: js-rendered-docs
  detail: Developer portal pages are HTML only and return no machine‑readable OpenAPI spec (e.g., https://developer.niceincontact.com/openapi.json
    redirects to a NotFound page).
  evidence:
  - url: https://developer.niceincontact.com/openapi.json
    status: 302
x-enrichment:
  date: '2026-10-14'
  status: enriched
  artifacts_added: 22
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

NICE API — frequently asked questions

Does NICE have an API?

Yes. APIs.io lists 11 APIs from NICE, including NICE Contact Center API, NICE Channels API and NICE Contacts API, and 8 more.

Is there an OpenAPI specification for the NICE API?

Yes. APIs.io indexes 10 OpenAPI specifications for NICE, each linked for download from this page.

How do I authenticate with the NICE API?

NICE uses bearer-token authentication (1 scheme). The details are profiled on APIs.io as Nice Authentication.

How much does the NICE API cost?

NICE publishes its prices; its Omnichannel Suite plan is $110 as of 2026-10-28. APIs.io lists 10 pricing plans for NICE, with each plan's price, limits and inclusions under Pricing on this page.

Is the NICE API ready for AI agents?

NICE has a Kin Score of 41.6 out of 100 (developing) and an Agent Readiness score of 23.9 (agent-aware), scored by API Evangelist on 2026-11-06.

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/nice"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/nice/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/nice/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.