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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Accredify0604

Accredify Nexus API

The Accredify Nexus platform API. OAuth 2.0 client-credentials REST API split across three published OpenAPI 3.1 modules: Auth (organisation users, groups, roles, user tokens, token issuance), Workflow (workflows, workflow runs, documents, design templates, document templates, courses) and Verification (verify a document, extract verifiable data keys). Nexus is also a live OID4VCI credential issuer serving mso_mdoc credentials for ISO/IEC 18013-5 mDL and ISO/IEC 23220 photo ID.

Documentation Provider Profile APIs.io OpenAPI GitHub

This API exposes 11 operations across 8 paths, organized into 5 resource areas, and defines 10 schemas. It is described by OpenAPI 3.1.0, at version 1.0.

Requests are made against 3 base URLs: https://nexus.staging.accredify.io, https://nexus.uat.accredify.io, https://nexus.accredify.io.

11 operations 8 paths 10 schemas 5 GET1 PATCH5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Base URL
https://nexus.accredify.io
Authentication
OAuth 2.0
Contact
Accredify
Terms of Service
View terms
Resource Areas
5

Authentication & Security 1

Accredify Nexus API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow, exposing 20 scopes.

  • OAuth2 — OAuth2 client credentials flow

Paths & Operations 11

Across 8 paths, the API surfaces 11 operations — 5 GET, 1 PATCH, 5 POST. They span 5 resource areas: OAuth, Organization Users, Organization Groups, Organization Roles, User Tokens. Each is listed below with its method, path, parameters, and response codes.

OAuth 1
POST
/oauth/token
Get OAuth access token
body → 200400401
Organization Users 4
GET
/api/v1/organization/users
Get list of organization users
6 params → 200401403422
POST
/api/v1/organization/users
Create an organization user
body → 201401403422
GET
/api/v1/organization/users/{user_uuid}
Get a specific organization user
1 param → 200401403404
PATCH
/api/v1/organization/users/{user_uuid}
Update an organization user
1 param body → 200401403404422
Organization Groups 2
GET
/api/v1/organization/groups
Get list of organization groups
7 params → 200401403422
POST
/api/v1/organization/groups/{group_uuid}/duplicate
Duplicate organization group
1 param body → 201401403404422
Organization Roles 1
GET
/api/v1/organization/roles
Get organization roles
→ 200401403
User Tokens 3
GET
/api/v1/organization/users/{user_uuid}/user_tokens
Get user tokens for an organization user
4 params → 200401403404422
POST
/api/v1/organization/users/{user_uuid}/user_tokens
Create a user token for an organization user
1 param body → 201401403404422
POST
/api/v1/organization/user_tokens/{token_uuid}/revoke
Revoke a user token
1 param → 200401403404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are PaginationMeta (8 properties), UserToken (7 properties), User (6 properties), OAuthTokenResponse (5 properties). Each schema is shown below with its type and property counts.

User
object
Organization user object
6 properties 6 required
Group
object
Organization group object
3 properties 3 required
Role
object
Organization role object
4 properties 4 required
UserToken
object
User token metadata object
7 properties 7 required
CreatedUserToken
CreatedUserTokenSecret
object
1 property 1 required
PaginationLinks
object
Pagination links for navigating through paginated results
4 properties 4 required
PaginationMeta
object
Pagination metadata containing information about the current page and total results
8 properties 8 required
OAuthTokenResponse
object
OAuth token response
5 properties 3 required
OAuthError
object
OAuth error response
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

accredify0604-nexus-auth-openapi.yaml Raw ↑
#Verifiable Credentials#Workflows#Document Verification#Identity#OID4VCI
← Back to A APIs
API Details
ID
accredify0604:accredify-nexus-api
Base URL
https://nexus.accredify.io
Docs
https://docs.nexus.accredify.io/
Provider
Accredify0604
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=accredify0604-accredify-nexus-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/accredify0604-accredify-nexus-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Accredify Nexus 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.