Account Management Biz Api
PATCH-billingAccountById
PATCH
This operation allows partial updates of a account entity. Attribute selection is enabled for all first level attributes.
Request
This section defines all the possible data structures sent by the client when consuming the method.
URL PARAMS
name | type | description | required |
---|---|---|---|
businessId | string | 2 letter ISO 3166 country code (TT, BB, JM, PA, etc.) identifying the business unit. | Y |
id | string | Unique identifier of the account | Y |
Security Headers
name | type | description | required |
---|---|---|---|
client_id | string | The client_id identifying the channel. Minimum characters: 5 | Y |
client_secret | string | Password associated with the client_id. Minimum characters: 5 | Y |
Header
name | type | description | required |
---|---|---|---|
X-Correlation-ID | string | Identifier that correlates HTTP request between a client and server. Any identification model (UUDI, checksum, etc.) can be used, as long as it is a unique value to differentiate a transaction. | N |
channelId | string | This is to identify the source (Project). Value : BUS sfdc-b2c Conditionally Mandatory. It is Mandatory only for B2B as there are underlying routing conditions based on channelId received Note: DEPRECATED, SHOULD NOT BE USED | Conditionally Mandatory |
lob | string | The Line of Business Identifier enum: ["FIXED", "PREPAID", "POSTPAID"] Note: DEPRECATED, SHOULD NOT BE USED | Conditionally Mandatory |
targetSystem | string | Use this data type to indicate target system name/id in your request. Note: DEPRECATED, SHOULD NOT BE USED | Conditionally Mandatory |
Body
Request Body for PA
{
"contact":[
{
"contactName": "Jodian Malcolm",
"partyRoleType": "OWNER",
"contactMedium":[
{
"mediumType":"Telephone",
"characteristic":{
"phoneNumber":"12345678",
"contactType": "home"
}
},
{
"mediumType":"Mobile",
"characteristic":{
"phoneNumber":"12345678",
"contactType": "mobile1"
}
},
{
"mediumType":"Mobile",
"characteristic":{
"phoneNumber":"12345678",
"contactType": "mobile2"
}
},
{
"mediumType":"Email",
"characteristic":{
"emailAddress":"alain.delon@best-actor.fr",
"contactType": "billEmail"
}
},
{
"mediumType":"Email",
"characteristic":{
"emailAddress":"alain.delon@best-actor.fr",
"contactType": "email"
}
}
]
},
{
"contactName": "Jodian",
"partyRoleType": "PORTIN",
"contactMedium":[
{
"mediumType":"Telephone",
"characteristic":{
"phoneNumber":"12345678",
"contactType": "home"
}
}
]
}
]
}
Note: contactName, partyRoleType, contactMedium.mediumType and contactMedium.contactType are mandatory fields to update contactMethod in the respective contacts.
Response
In this section all the possible data structures received by the client at the moment of responding the method are defined.
Possible response success
This section defines all the possible data structures received by the client and that must be considered satisfactory at the time of responding to the method.
[ 200 ]
OK - PATCH request processed successfully, response body contains an entity corresponding to the requested resource.
{
"contact":[
{
"contactName": "Jodian Malcolm",
"partyRoleType": "OWNER",
"contactMedium":[
{
"mediumType":"Telephone",
"characteristic":{
"phoneNumber":"12345678",
"contactType": "home"
}
},
{
"mediumType":"Mobile",
"characteristic":{
"phoneNumber":"12345678",
"contactType": "mobile1"
}
},
{
"mediumType":"Mobile",
"characteristic":{
"phoneNumber":"12345678",
"contactType": "mobile2"
}
},
{
"mediumType":"Email",
"characteristic":{
"emailAddress":"alain.delon@best-actor.fr",
"contactType": "billEmail"
}
},
{
"mediumType":"Email",
"characteristic":{
"emailAddress":"alain.delon@best-actor.fr",
"contactType": "email"
}
}
]
},
{
"contactName": "Jodian",
"partyRoleType": "PORTIN",
"contactMedium":[
{
"mediumType":"Telephone",
"characteristic":{
"phoneNumber":"12345678",
"contactType": "home"
}
}
]
}
]
}