Download OpenAPI specification:Download
Operations exposed by the Issuer Bank for amiko to integrate with. For additional guidance around this integration API, see the relevant section in the Amiko documentation.
To request a safe identifier matched to a PAN. See the Amiko documentation for additional requirements on this endpoint
| tracing-id required | string Tracing ID that can be used to track interactions. |
| auth_header | string The given http header "auth_header" should be considered only a placeholder in this OpenAPI spec. The actual header name and header value must match the configured authentication strategy e.g. API Key or JWT. |
| pan required | string <[0-9]{13,19}> Primary Account Number of the card |
{- "pan": "string"
}{- "cardId": "string"
}To resolve a cardId into a PAN, used for scheme-facing operations.
| cardId required | string |
| tracing-id required | string Tracing ID that can be used to track interactions. |
| auth_header | string The given http header "auth_header" should be considered only a placeholder in this OpenAPI spec. The actual header name and header value must match the configured authentication strategy e.g. API Key or JWT. |
{- "pan": "string"
}To retrieve the identifier of the holder of the card
| cardId required | string |
| tracing-id required | string Tracing ID that can be used to track interactions. |
| auth_header | string The given http header "auth_header" should be considered only a placeholder in this OpenAPI spec. The actual header name and header value must match the configured authentication strategy e.g. API Key or JWT. |
{- "cardholderId": "string"
}To retrieve if the cardholder can be reached via a digital channel (Dialgoue Engine) and optionally type of that channel
| cardholderId required | string |
| tracing-id required | string Tracing ID that can be used to track interactions. |
| auth_header | string The given http header "auth_header" should be considered only a placeholder in this OpenAPI spec. The actual header name and header value must match the configured authentication strategy e.g. API Key or JWT. |
{- "contactable": true,
- "channel": [
- {
- "label": "string",
- "type": "app"
}
]
}To retrieve additional attributes related to the card currency, the issuer and cardholder-facing brand
| cardId required | string |
| tracing-id required | string Tracing ID that can be used to track interactions. |
| auth_header | string The given http header "auth_header" should be considered only a placeholder in this OpenAPI spec. The actual header name and header value must match the configured authentication strategy e.g. API Key or JWT. |
{- "issuerId": "string",
- "issuerName": "string",
- "brandId": "string",
- "brandName": "string",
- "currencyCode": "string"
}Returns the expiry month and year for a cardId
| cardId required | string |
| tracing-id required | string Tracing ID that can be used to track interactions. |
| auth_header | string The given http header "auth_header" should be considered only a placeholder in this OpenAPI spec. The actual header name and header value must match the configured authentication strategy e.g. API Key or JWT. |
{- "expiryMonth": "string",
- "expiryYear": "string"
}Information on whether the card is active, suspended (temporarily) or blocked (permanently). In the case of a blocked card, also the information on the block reason.
| cardId required | string |
| tracing-id required | string Tracing ID that can be used to track interactions. |
| auth_header | string The given http header "auth_header" should be considered only a placeholder in this OpenAPI spec. The actual header name and header value must match the configured authentication strategy e.g. API Key or JWT. |
{- "status": "active",
- "blockReason": "lost_stolen",
- "fraudType": "first_party_fraud"
}To retrieve the cardholder name and generic additional attributes of the cardholder. The returned values will not be stored by Amiko and are only requested on demand to be displayed on the agent UI.
| cardholderId required | string |
| tracing-id required | string Tracing ID that can be used to track interactions. |
| auth_header | string The given http header "auth_header" should be considered only a placeholder in this OpenAPI spec. The actual header name and header value must match the configured authentication strategy e.g. API Key or JWT. |
{- "name": "string",
- "languageCode": "string",
- "attributes": [
- {
- "label": "string",
- "value": "string"
}
]
}The specification is based on the IETF draft https://inadarei.github.io/rfc-healthcheck/.
Please refer to our Health Check documentation for more information.
| auth_header | string This is going to be where we send the API key. The header will consist of a custom api key or standardised JWT auth. |
{- "status": "fail"
}