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 Update card API

Endpoints for updating a card

Enfuce Update card API is one of 7 APIs that Enfuce publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Update card. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 5 paths, and defines 27 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.

5 operations 5 paths 27 schemas 1 PATCH4 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 Update card API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 5

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

Update card 5

Endpoints for updating a card

PATCH
/v1/cards/{id}
Partially Update Card
patchCard 2 params body → 200400401403404409500
POST
/v1/cards/{id}/replace
Replace Card
replaceCard 3 params body → 200400401403404409500
POST
/v1/cards/{id}/reissue
Reissue Card
reissueCard 3 params body → 200400401403404409500
POST
/v1/cards/{id}/activate
Activate Card
activateCard 3 params → 200400401403404409500
POST
/v1/cards/{id}/reorder-pin
Reorder PIN for Card
reorderPin 3 params → 200400401403404500

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are UpdateCardBody (15 properties), Address (8 properties), ErrorResponse (7 properties), UpdatePlasticBody (7 properties). Each schema is shown below with its type and property counts.

AutomaticRenewal
boolean
A flag indicating whether automatic renewal is enabled or not.
CardDeliveryType
string
Select the type of delivery you prefer for the new card being created. - MAIL - The card would be sent via mail services. - COURIER - The card would be sent vi…
AccountId
string
Unique identifier of an account.
Id
string
Unique identifier of a resource.
ChipEnabled
boolean
Whether the card should be visible in card terminal or not. Only applicable to multi-application cards. Otherwise, the request will return 400 Bad Request.
UpdatePinStatus
string
- GENERATED - A pin should be randomly generated for the card.
ContactPriorityLevel
integer
The contact priority level for given card. Only applicable to multi-application cards. Otherwise, the request will return 400 Bad Request.
DigitalLayoutCode
string
The digital layout code for the card. Max character limit is 36.
EmbossingName
string
The name to be embossed on the card. Max character limit is 26.
ReplaceCardBody
object
2 properties
Printed
boolean
Indicates whether the specific card would be printed or not. Only applicable to multi-application cards. Otherwise, the request will return 400 Bad Request.
UpdateCardBody
object
15 properties
ImpactTokenStatus
boolean
If set to true, the card status change will impact the status of all tokens. If set to false, the card status change will not impact the status of all tokens.
PinDeliveryType
string
Select the type of delivery you prefer for sending the card PIN. - MAIL - The card PIN would be sent via mail services. - COURIER - The card PIN would be sent…
ErrorResponse
object
7 properties
ReissueCardBody
object
1 property
ResourceResponse
object
2 properties
ApplicationName
string
Name of the application. Max character limit is 16. Only applicable to multi-application cards. Otherwise, the request will return 400 Bad Request.
UpdatePlasticBody
object
7 properties
CardStatus
string
- ACTIVE - Card is active and is enabled for normal usage. - BLOCKED - Card is temporarily blocked. - BLOCKEDSUSPECTEDFRAUD - Card is temporarily blocked due t…
ExternalLayoutCode
string
Unique code forwarded to the embossing house; the code identifies the plastic layout to be used for printing the new card. Ensure beforehand, the selected embo…
FeeConfigId
string
Unique identifier of a fee configuration. When provided, this value overrides the program default. This feature must be enabled for the tenant; otherwise, this…
Address
object
8 properties 4 required
ContactlessPriorityLevel
integer
The contactless priority level of the given card. Only applicable to multi-application cards. Otherwise, the request will return 400 Bad Request.
OptionalId
stringnull
Unique identifier of an entity.
AdditionalValues
object
You can include up to 30 additional key-value pairs in the embossing file sent to the card manufacturer. - Keys must follow the pattern: ^[a-zA-Z0-9-]{1,36}$ (…
ChangePinStatus
string
- GENERATED - A pin should be randomly generated for the card. - WAITING - A pin is waiting to be set on the card.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

enfuce-update-card-api-openapi.yml Raw ↑

Other APIs Enfuce publishes across the network.

Enfuce Authorisation Request API
Enfuce Create Card API
Enfuce Create PIN Control access token API
Enfuce Get card API
Enfuce Get Card Payment Info API
Enfuce Get plastic manufacturing history API
Where this information came from

This is an independent, third-party profile of Enfuce Update card 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.