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

Enfuce Create PIN Control access token API

The Create PIN Control access token API from Enfuce — 1 operation(s) for create pin control access token.

Enfuce Create PIN Control access token API is one of 7 APIs that Enfuce publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Create PIN Control access token. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 1 operation across 1 path, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against 2 base URLs: https://api.{{tenant}}.ext-uat1-sandbox.mycore.enfuce.com/issuer, https://api.{{tenant}}.eu.live.prod.mycore.enfuce.com/issuer.

1 operations 1 paths 6 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.{{tenant}}.eu.live.prod.mycore.enfuce.com/issuer
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Enfuce Create PIN Control access token API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Create PIN Control access token 1
POST
/v1/cards/{id}/pinControl
Request PIN Control Access Token
createPinControl 2 params body → 201400401403404500

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ErrorResponse (7 properties), PinControlInfoResponseBody (3 properties), PinControlInfoRequestBody (2 properties). Each schema is shown below with its type and property counts.

PinControlInfoResponseBody
object
3 properties 1 required
PinScope
string
Describes the scope of the operation authorised by the user.
PinControlInfoRequestBody
object
2 properties 1 required
Id
string
Unique identifier of a resource.
SequenceNumber
integer
The sequence number of the card version, this value is also known as PSN (pan sequence number)
ErrorResponse
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

enfuce-create-pin-control-access-token-api-openapi.yml Raw ↑

Other APIs Enfuce publishes across the network.

Enfuce Authorisation Request API
Enfuce Create Card API
Enfuce Get card API
Enfuce Get Card Payment Info API
Enfuce Get plastic manufacturing history API
Enfuce Update card API
Where this information came from

This is an independent, third-party profile of Enfuce Create PIN Control access token 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.