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

Mastercard Developer Hub for FDX APIs Dynamic Client Registration API

As per [RFC 7591 - OAuth 2.0 Dynamic Client Registration Protocol (ietf.org)](https://datatracker.ietf.org/doc/html/rfc7591)

Mastercard Developer Hub for FDX APIs Dynamic Client Registration API is one of 10 APIs that Mastercard Developer Hub for FDX APIs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Dynamic Client Registration. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 4 operations across 2 paths, and defines 18 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against a single base URL, http://localhost:8080.

4 operations 2 paths 18 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
http://api.example.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Mastercard Developer Hub for FDX APIs Dynamic Client Registration API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth).

Paths & Operations 4

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

Dynamic Client Registration 4

As per [RFC 7591 - OAuth 2.0 Dynamic Client Registration Protocol (ietf.org)](https://datatracker.ietf.org/doc/html/rfc7591)

POST
/fdx/v6/register
Mastercard Developer Hub for FDX APIs Client Registration Request
registerClient body → 200
GET
/fdx/v6/register/{clientId}
Mastercard Developer Hub for FDX APIs Get Client
getClient 1 param → 200
PUT
/fdx/v6/register/{clientId}
Mastercard Developer Hub for FDX APIs Update Client
modifyClient 1 param body → 200
DELETE
/fdx/v6/register/{clientId}
Mastercard Developer Hub for FDX APIs Delete Client
deleteClient 1 param → 204

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are CreateClient (13 properties), Client (12 properties). Each schema is shown below with its type and property counts.

Client
object
12 properties
jwks_uri
string
URL string referencing the client's JSON Web Key (JWK) Set [RFC7517] document, which contains the client's public keys
id_token_signed_response_alg
string
Algorithm with which an idtoken is to be signed
grant_types
array
Array of OAuth 2.0 grants made available to the Data Recipient
client_id
string
OAuth 2.0 client identifier. Unique ID representing Data Recipient and Identity Chain combination
id_token_encrypted_response_enc
string
JWE enc algorithm with which an idtoken is to be encrypted.
client_id_issued_at
number
Time at which the clientid was issued (measured in unix seconds)
redirect_uris
array
Array of redirection URI strings for use in redirect-based flows
token_endpoint_auth_method
string
Requested authentication method for the token endpoint.
client_name
string
Human-readable string name of the client application
CreateClient
object
13 properties
response_types
array
Array of OAuth 2.0 response type strings. Default value is code
registration_access_token
string
String containing a unique DCR access token to be used in subsequent operations to manage the Data Recipient
request_object_signing_alg
string
Algorithm which the client expects to sign the request object if a request object will be part of the authorization request sent to the Data Holder
id_token_encrypted_response_alg
string
JWE alg algorithm with which an idtoken is to be encrypted.
scope
string
String containing a space-separated list of scope values that the client can use when requesting access tokens.
token_endpoint_auth_signing_alg
string
The algorithm used for signing the JWT
registration_client_uri
string
Fully qualified URI for subsequent DCR calls (GET, PUT, DELETE) for managing the Data Recipient registration

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mastercard-developer-hub-for-fdx-apis-dynamic-client-registration-api-openapi.yml Raw ↑

Other APIs Mastercard Developer Hub for FDX APIs publishes across the network.

Mastercard Developer Hub for FDX APIs Application Check Controller API
Mastercard Developer Hub for FDX APIs Consent API
Mastercard Developer Hub for FDX APIs Data Resource APIs API
Mastercard Developer Hub for FDX APIs Non PAR Authorize API
Mastercard Developer Hub for FDX APIs PAR+RAR Authorize API
Mastercard Developer Hub for FDX APIs Resource Token API
Mastercard Developer Hub for FDX APIs Token Introspection API
Mastercard Developer Hub for FDX APIs Upload Data API
Mastercard Developer Hub for FDX APIs User APIs API
Where this information came from

This is an independent, third-party profile of Mastercard Developer Hub for FDX APIs Dynamic Client Registration 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.