---
swagger: "2.0"
info:
title: csmt-crd-o-identify-customer-detail
description: This microservices orchestrates the call of 2 adapters where the client
information for the homonymy query is obtained from Mongo DB and S016
version: 1.0.0
x-ibm-name: csmt-crd-o-identify-customer-detail
host: 127.0.0.1
schemes:
- https
basePath: /api
produces:
- application/json
paths:
/v1/customers/search/info/retrieve:
post:
tags:
- retrieve-customers-search-info
operationId: retrieve-customers-search-info
summary: 'LOB:Customer Data, Feature: Customer Ambiguity Functionality: Customer
search details'
description: Check the customer data and their Mongo and S016 accounts according
to the combination of data in the search.
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
description: The Authorization Token received during login
type: string
required: true
- name: Accept
in: header
description: Content-Types that are acceptable for the response
type: string
required: true
- name: uuid
in: header
description: 128 bit UUID that you generate for every request
type: string
required: true
- name: Accept-Language
in: header
description: List of acceptable human languages for response
type: string
required: false
- name: Content-Type
in: header
description: Content-Types that are sent in the request
required: true
type: string
- 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
description: SessionId sent by Consumer
required: true
type: string
- name: customerSearchInfoRequest
in: body
schema:
$ref: '#/definitions/CustomerSearchInfoRequest'
responses:
200:
description: Successful operation.
schema:
$ref: '#/definitions/CustomerSearchInfoResponse'
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'
/v1/customers/detailed-history/retrieve:
post:
tags:
- retrieve-customer-detailed-history
operationId: retrieve-customer-detailed-history
summary: 'LOB:Customer Data, Feature: Customer Ambiguity, Functionality: Customer
Detailed History'
description: This API queries the data of the additional customers returned
by the first API according to their customerID since there may be customers
with more than one customerID
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
description: The Authorization Token received during login
type: string
required: true
- name: Accept
in: header
description: Content-Types that are acceptable for the response
type: string
required: true
- name: uuid
in: header
description: 128 bit UUID that you generate for every request
type: string
required: true
- name: Accept-Language
in: header
description: List of acceptable human languages for response
type: string
required: false
- name: Content-Type
in: header
description: Content-Types that are sent in the request
required: true
type: string
- 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
description: SessionId sent by Consumer
required: true
type: string
- name: customerDetailedHistoryRequest
in: body
schema:
$ref: '#/definitions/CustomerDetailedHistoryRequest'
responses:
200:
description: Successful operation.
schema:
$ref: '#/definitions/CustomerDetailedHistoryResponse'
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:
CustomerSearchInfoRequest:
type: object
properties:
encryptedCustomerSearchInfoDetail:
type: string
example: WTq8zYcZfaWVvMncigHqwQ==
description: Encrypted field containing validate object.
CustomerDetailedHistoryRequest:
type: object
properties:
customerId:
description: Unique identifier of the customer.
type: string
example: "123456789012"
CustomerSearchInfoResponse:
type: object
properties:
customerDetail:
type: array
items:
$ref: '#/definitions/CustomerDetail'
CustomerDetailedHistoryResponse:
type: object
properties:
customerDetail:
type: array
items:
$ref: '#/definitions/CustomerInfo'
CustomerDetail:
type: object
properties:
encryptedCustomerDetail:
description: Encrypted field containing validate object.
type: string
example: WTq8zYcZfaWVvMncigHqwQ==
CustomerInfo:
type: object
properties:
encryptedCustomerInfoDetail:
description: Encrypted field containing validate object.
type: string
example: WTq8zYcZfaWVvMncigHqwQ==
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: URI to human readable documentation or detailed description 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
...