---
swagger: "2.0"
info:
title: crds-ccc-v-card-plastic-servicing
description: This microservice is used as an view service related to the functionality
to lock and unlock credit and debit cards.
version: 1.0.0
x-ibm-name: crds-ccc-v-card-plastic-servicing
host: 127.0.0.1
schemes:
- https
basePath: /api
produces:
- application/json
paths:
/v1/cards/card-plastics/lock-unlock-info:
put:
tags:
- card-plastic-lock-unlock-info
operationId: card-plastic-lock-unlock-info
summary: 'LOB: Cards, Feature: Card Plastic, Functionality: Lock and Unlock
Cards Plastic'
description: This API will be retriving information from the account to enable
customers the functionality to lock and unlock temporarily their cards.
consumes:
- application/json
produces:
- application/json
parameters:
- name: client_id
in: header
required: true
type: string
description: Client ID generated during application registration
- name: Authorization
in: header
required: true
type: string
description: The Authorization Token received during login
- name: Accept
in: header
required: true
type: string
description: Content-Types that are acceptable for the response
- name: uuid
in: header
required: true
type: string
description: 128 bit UUID that you generate for every request
- name: Accept-Language
in: header
required: false
type: string
description: List of acceptable human languages for response
- name: Content-Type
in: header
required: true
type: string
description: Content-Types that are sent in the request
- name: ChannelId
in: header
required: true
type: string
description: Channel where request originated
- name: countryCode
in: header
required: true
type: string
description: Country code in 2 character ISO 3166 format
- name: businessCode
in: header
required: true
type: string
description: Business code identified during application registration
- name: sid
in: header
required: true
type: string
description: SessionId sent by Consumer
- name: cardPlasticLockUnlockInfoRequest
in: body
schema:
$ref: '#/definitions/CardPlasticLockUnlockInfoRequest'
responses:
200:
description: Successful operation.
schema:
$ref: '#/definitions/CardPlasticLockUnlockInfoResponse'
400:
description:
Type | Code | Details |
error | invalidRequest | Missing
or invalid Parameters |
schema:
$ref: '#/definitions/ErrorResponse'
401:
description: Type | Code | Details |
error | unAuthorized | Authorization
credentials are missing or invalid |
schema:
$ref: '#/definitions/ErrorResponse'
403:
description: Type | Code | Details | More
Info |
error | accessNotConfigured | The request
operation is not configured to access this resource | Channel/Country/Business
provided in the request is not supported currently |
schema:
$ref: '#/definitions/ErrorResponse'
404:
description: Type | Code | Details | More
Info |
error | resourceNotFound | The requested
resource was not found | Empty resource/resource not found |
schema:
$ref: '#/definitions/ErrorResponse'
422:
description: Type | Code | Details |
error | businessValidationFailed | Business
validation error occured on one or more parameters |
schema:
$ref: '#/definitions/ErrorResponse'
500:
description: Type | Code | Details |
fatal | serverUnavailable | The
request failed due to an internal error/server unavailability |
schema:
$ref: '#/definitions/ErrorResponse'
definitions:
CardPlasticLockUnlockInfoRequest:
type: object
properties:
cardLockedFlag:
description: The flag used to indicate if should be lock or unlock a particular
card. True for lock card or false for unlock card.
type: boolean
example: true
customerId:
description: Customer ID is a key associated with a specific entity or person
Citi does business or has some relationship with
type: string
pattern: ^[0-9]{5,12}$
minLength: 5
maxLength: 12
example: "123456789012"
accountId:
description: Unique ID used by front end to identify the account
type: string
example: "123456"
required:
- cardLockedFlag
- customerId
- accountId
CardPlasticLockUnlockInfoResponse:
type: object
properties:
operationReferenceNumber:
description: Unique refrence number to identify the operation. It is generated
by the folio operation service, used for tracking
type: string
example: 0328dm64sjdh384m02
operationDate:
description: Date and time that indicate when card was lock or unlock
type: string
format: date-time
example: "2021-04-22T05:22:25Z"
cardLockedFlag:
description: The flag used to indicate if should be lock or unlock a particular
card. True for lock card or false for unlock card.
type: boolean
example: true
required:
- operationReferenceNumber
- operationDate
- cardLockedFlag
ErrorResponse:
properties:
type:
type: string
description: Invalid - Request did not confirm to the specification and was
unprocessed and rejected. Please fix the value and try again
enum:
- error
- warn
- invalid
- fatal
code:
description: Error code which qualifies the error
type: string
details:
description: Human readable explanation specific to the occurrence of the
problem
type: string
location:
description: The name of the field that resulted in the error
type: string
moreInfo:
description: More Info can be used to pass any additional details
type: string
uuid:
description: 128 bit UUID that you generate for every request
type: string
timestamp:
description: Timestamp of the error
type: string
required:
- type
- code
x-ibm-configuration:
enforced: true
testable: true
phase: realized
securityDefinitions:
OAuth2 Application Flow:
type: oauth2
description: ""
flow: application
scopes:
/api/v1: ""
tokenUrl: https://perf.api.externalapib2b.wlb.lac.nsroot.net:7100/mx-gcgapi/perfext/api/v1/oauth/token
Client ID:
type: apiKey
description: ""
in: header
name: X-IBM-Client-Id
security:
- OAuth2 Application Flow:
- /api/v1
Client ID: []
x-ibm-endpoints:
- endpointUrl: https://perf.api.externalapib2b.wlb.lac.nsroot.net:7100/mx-gcgapi/perfext
type:
- production
- development
...