--- swagger: "2.0" info: title: CRDS-CCC-V-DbCardMnt description: The Microservice helps to consume S054 back end service in order to perform operations over debit cards. version: 1.0.0 x-ibm-name: crds-ccc-v-dbcardmnt host: 127.0.0.1 schemes: - https basePath: /api produces: - application/json paths: /v1/cards/debit/lock-unlock/detail: post: tags: - debit-card-lock-unlock operationId: debit-card-lock-unlock summary: To lock and unlock debit card if the customer detect unusual transactions. description: This API will lock and unlock debit cards, this is a soft mark that can be applied if the customer detect unusual transactions in their debit card 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: lockUnlockRequest in: body required: true schema: $ref: '#/definitions/LockUnlockRequest' responses: 200: description: Successful operation. schema: $ref: '#/definitions/LockUnlockResponse' 400: description:
TypeCodeDetails
errorinvalidRequestMissing or invalid Parameters
schema: $ref: '#/definitions/ErrorResponse' 401: description:
TypeCodeDetails
errorunAuthorizedAuthorization credentials are missing or invalid
schema: $ref: '#/definitions/ErrorResponse' 403: description:
TypeCodeDetailsMore Info
erroraccessNotConfiguredThe request operation is not configured to access this resourceChannel/Country/Business provided in the request is not supported currently
schema: $ref: '#/definitions/ErrorResponse' 404: description:
TypeCodeDetailsMore Info
errorresourceNotFoundThe requested resource was not foundEmpty resource/resource not found
schema: $ref: '#/definitions/ErrorResponse' 422: description:
TypeCodeDetails
errorbusinessValidationFailedBusiness validation error occured on one or more parameters
schema: $ref: '#/definitions/ErrorResponse' 500: description:
TypeCodeDetails
fatalserverUnavailableThe request failed due to an internal error/server unavailability
schema: $ref: '#/definitions/ErrorResponse' definitions: LockUnlockRequest: type: object properties: cardBlockCode: description: The block code used to block a particular card. Card Block Codes are Temp. Block, Lost, Fraud / Stolen, Over Credit Limit. M - soft lock, U - remove soft lock type: string enum: - M - U example: M customerId: description: Unique identifier of the customer type: string pattern: ^[0-9]{1,12}$ example: "123456789012" maxLength: 12 accountId: description: Unique ID used by front end to indentify the account type: string example: "123456" required: - cardBlockCode - customerId - accountId LockUnlockResponse: type: object properties: responseMessage: type: string example: TRANSACTION SUCCESSFULLY APPLIED description: 'Message from the back end about of the result of the operation ' required: - responseMessage 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 ...