---
swagger: "2.0"
info:
title: CSMT-CRM-V-CodiBanxicoDeviceManagementView
description: The microservice helps to manage the devices in Banxico for Codi feature.
This is the View swagger at the Edge layer.
version: 1.0.0
x-ibm-name: csmt-crm-v-codibanxicodevicemanagementview
host: 127.0.0.1
schemes:
- https
basePath: /api
produces:
- application/json
paths:
/v1/customers/codi-banxico/devices/register/detail:
post:
tags:
- register-codi-device-info
operationId: register-codi-device-info
summary: To register the device and application detail in Banxico for Codi feature
description: The API will register the device and application detail in Banxico
for Codi feature
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: registerCodiDeviceRequest
in: body
schema:
$ref: '#/definitions/RegisterCodiDeviceRequest'
responses:
200:
description: Successful operation.
schema:
$ref: '#/definitions/RegisterCodiDeviceResponse'
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/codi-banxico/devices/validate/detail:
post:
tags:
- validate-codi-device-info
operationId: validate-codi-device-info
summary: The API helps to validate the device and application detail with Banxico
for Codi feature
description: The API helps to validate the device and application detail with
Banxico for Codi feature
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: validateCodiCustomerRequest
in: body
schema:
$ref: '#/definitions/ValidateCodiCustomerRequest'
responses:
200:
description: Successful operation.
schema:
$ref: '#/definitions/ValidateCodiCustomerResponse'
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/codi-banxico/applications/set-default/detail:
post:
tags:
- set-codi-default-application-info
operationId: set-codi-default-application-info
summary: The API helps to set the default banking application for Codi
description: The API helps to set the default banking application for Codi
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: setDefaultApplicationRequest
in: body
schema:
$ref: '#/definitions/SetDefaultApplicationRequest'
responses:
200:
description: Successful operation.
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/codi-banxico/devices/detail/delete:
put:
tags:
- delete-codi-device-info
operationId: delete-codi-device-info
summary: To delete the device registry in Banxico for Codi feature
description: This API is used to delete the device registry in Banxico for Codi
feature
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: deleteDeviceRequest
in: body
schema:
$ref: '#/definitions/DeleteDeviceRequest'
responses:
200:
description: Successful operation.
schema:
$ref: '#/definitions/DeleteDeviceResponse'
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:
RegisterCodiDeviceRequest:
type: object
properties:
deviceDetails:
$ref: '#/definitions/Device'
Device:
type: object
properties:
deviceMake:
description: Maker of the device which the client is using to enroll with
Citibanamex CoDi
type: string
example: samsung
deviceModel:
description: Model of the device which the client is using to enroll with
Citibanamex CoDi
type: string
example: SM-G935F
deviceOsId:
description: ID of the Operative system of the device with the client is using
to enroll with Citibanamex CoDi
type: string
example: "01"
deviceOsName:
description: Operative system of the device with the client is using to enroll
with Citibanamex CoDi
type: string
example: Android
deviceOsVersion:
description: Version of the operative system of the device which the user
is using to enroll with Citibanamex CoDi
type: string
example: 8.0.0
deviceSerialNumber:
description: Serial number of the device which a new user is enrolling with
Citibanamex CoDi
type: string
example: 12d58955dcd9e1f4-com.citibanamex.banamexmobile
required:
- deviceMake
- deviceModel
- deviceOsName
- deviceOsVersion
- deviceSerialNumber
RegisterCodiDeviceResponse:
type: object
properties:
encryptedCodiDeviceId:
description: Encrypted alias asigned by Banxico to identify the device uniquely
type: string
example: asfsSRTaxderty$%5fwe==
codiBankingAppId:
description: Check code assigned by Banxico to identify the App in the device
type: integer
example: 1
encryptedGoogleId:
description: Encrypted Id of the project enrolled with Google in order to
request a new FirebaseId releated to the project
type: string
example: 4OIemuIf04sMzbFBl_duDoWZOO4rADGviq0Rf4UCz-cYS6zvijYesfRbUR1a4BQqKUQ4z56cgmTyEjtQdQQgIz
required:
- encryptedCodiDeviceId
- codiBankingAppId
- encryptedGoogleId
ValidateCodiCustomerRequest:
type: object
properties:
firebaseId:
description: Firebase id of the customer registered with Banxico in order
to receive PUSH notifications
type: string
example: dUww7Jl4b9o:APA91bGHVzEMF6xdD_ZV1L4CF5ZgrBqDQGl9QO4OIemuIf04sMzbFBl_duDoWZOO4rADGviq0Rf4UCz-cYS6zvijYesfRbUR1a4BQqKUQ4z56cgmTyEjtQdQQgIz_-8KLRxmJdI9571o
codiDeviceId:
description: Alias asigned by Banxico to identify the device uniquely
type: string
example: "460912423578"
codiBankingAppId:
description: Check code assigned by Banxico to identify the App in the device
type: integer
example: 1
messageAuthenticationCode:
description: Hashed message authentication code (HMAC) needed by Banxico to
validate the request's authenticity
type: string
example: dUww7Jl4b9o:APA91bCF5ZgrBqDQGl9QO4OIemuIf-cYS6zvijYesf
deviceInfo:
$ref: '#/definitions/DeviceInfo'
required:
- firebaseId
- codiDeviceId
- codiBankingAppId
- deviceInfo
- messageAuthenticationCode
DeviceInfo:
type: object
properties:
deviceMake:
description: Maker of the device which the client is using to enroll with
Citibanamex CoDi
type: string
example: samsung
deviceModel:
description: Model of the device which the client is using to enroll with
Citibanamex CoDi
type: string
example: SM-G935F
deviceOsId:
description: ID of the Operative system of the device with the client is using
to enroll with Citibanamex CoDi
type: string
example: "01"
deviceOsName:
description: Operative system of the device with the client is using to enroll
with Citibanamex CoDi
type: string
example: Android
deviceOsVersion:
description: Version of the operative system of the device which the user
is using to enroll with Citibanamex CoDi
type: string
example: 8.0.0
deviceSerialNumber:
description: Serial number of the device which a new user is enrolling with
Citibanamex CoDi
type: string
example: 12d58955dcd9e1f4-com.citibanamex.banamexmobile
required:
- deviceMake
- deviceModel
- deviceOsName
- deviceOsVersion
- deviceSerialNumber
ValidateCodiCustomerResponse:
type: object
properties:
codiBankingAppId:
description: Check code assigned by Banxico to identify the App in the device
type: integer
example: 1
codiBankingDefaultAppId:
description: Check code that Banxico has for the default application in the
device to get notifications
type: integer
example: 2
required:
- codiBankingAppId
- codiBankingDefaultAppId
SetDefaultApplicationRequest:
type: object
properties:
codiDeviceId:
description: Alias asigned by Banxico to identify the device uniquely
type: string
example: "460912423578"
codiBankingAppId:
description: Check code assigned by Banxico to identify the App in the device
type: integer
example: 1
messageAuthenticationCode:
description: Hashed message authentication code (HMAC) needed by Banxico to
validate the request's authenticity
type: string
example: dUww7Jl4b9o:APA91bCF5ZgrBqDQGl9QO4OIemuIf-cYS6zvijYesf
required:
- codiDeviceId
- codiBankingAppId
- messageAuthenticationCode
DeleteDeviceRequest:
type: object
properties:
devices:
type: array
items:
$ref: '#/definitions/DeviceData'
required:
- devices
DeviceData:
type: object
properties:
codiBankingAppId:
description: Check code assigned by Banxico to identify the App in the device
type: integer
example: 1
firebaseId:
description: Firebase id of the customer registered with Banxico in order
to receive PUSH notifications
type: string
example: dUww7Jl4b9o:APA91bGHVzEMF6xdD_ZV1L4CF5ZgrBqDQGl9QO4OIemuIf04sMzbFBl_duDoWZOO4rADGviq0Rf4UCz-cYS6zvijYesfRbUR1a4BQqKUQ4z56cgmTyEjtQdQQgIz_-8KLRxmJdI9571o
required:
- codiBankingAppId
DeleteDeviceResponse:
type: object
properties:
responses:
type: array
items:
$ref: '#/definitions/Response'
required:
- responses
Response:
type: object
properties:
responseCode:
description: Response code for each phone sent in the array, according to
its position
type: string
example: "0"
responseDescription:
description: Response description for each phone sent in the array, accordign
to its position
type: string
example: Device Deleted successfully
required:
- responseCode
- responseDescription
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
...