b2bsoft-ux
stockCountResults
Synchronization of count stock between SAP and B2B Soft.
URL
https://[localhost]:[port]/b2bsoft-ux/v1/{businessId}/stockCountResults
URL PARAMS
name | type | description | required |
---|---|---|---|
businessId | string | 2 letter ISO 3166 country code (TT, BB, JM, PA, PR, CR etc.) identifying the business unit. | Y |
Header
name | value | 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 |
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. Note - Mule default behavior creates a sample x-correlation-id field if value is not passed from client, API will use this value in case value is not passed in API request | N |
cURL Request
curl --location 'https://nonprod.esb.cloud.lla.com/dev/b2bsoft-ux/b2bsoft-ux/v1/PR/stockCountResults' \
--header 'client_id: abcde' \
--header 'client_secret: 12345' \
--header 'Content-Type: application/json' \
--data-raw '{
"header":{
"postingDate":"20250129",
"docDate":"20250129",
"storeId":"13PR",
"locationId":"002",
"action":"stockCountResultsB2B"
},
"diffQty":"NA",
"items":[
{
"SKU":"000000000000103130",
"batch":"TEST2",
"serialNo":"100000000824001",
"entryQuantity":1.000
}
]
}'
Each of the request parameters is detailed.
Name | Type | Description | Required |
---|---|---|---|
header | object | Consists the header details of the stock | Y |
header.postingDate | String | Goods movement posting date | Y |
header.docDate | String | Goods movement documented / requested date | Y |
header.storeId | String | Storage location | Y |
header.locationId | String | Location id to indicate Retails/Returns | Y |
header.action | String | Operation being performed | Y |
diffQty | String | Difference in Quantity | Y |
items | array | Array of stock details | Y |
items.SKU | String | Unique identifier of the material/product | Y |
items.batch | String | Batch Number of the stock item | Y |
items.serialNo | String | Serial Number of the stock item | Y |
items.entryQuantity | String | Stock quantity | Y |
Response
{
"id":"2022",
"description": "4900001465"
}
Definitions
Each of the request parameters is detailed.
name | value | description | required |
---|---|---|---|
id | string | Document created year | Y |
description | string | Reference number of the goods movement | Y |
Possible response error
In this section all the possible data structures received by the client are defined and that must be considered as unsatisfactory when responding to the method.
[ 400 ]
Bad Request - the request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
{
"errors": [
{
"code": 400,
"message": "VALIDATION:MISMATCH",
"description": "Invalid Posting Date, it should be in yyyymmdd format"
}
]
}
[ 401 ]
Unauthorized - The request has not been applied because it lacks valid authentication credentials for the target resource.
{
"errors" : [{
"code" : 401,
"message" : "The user could not be authenticated for this request.",
"description" : "The request has not been applied because it lacks valid authentication credentials for the target resource."
}]
}
[ 404 ]
Not Found - server has not found a resource with that URI. This may be temporary and permanent condition. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
{
"errors" : [{
"code" : 404,
"message" : "The server could not find the requested resource.",
"description" : "The requested operation failed because a resource associated with the request could not be found."
}]
}
[ 405 ]
Method Not Allowed - HTTP method not allowed for this resource. The method specified in the Request-Line is not allowed for the resource identified by the Request-URI.
{
"errors": [{
"code": 405,
"message": "APIKIT:METHOD_NOT_ALLOWED",
"description": "HTTP Method DELETE not allowed for : /{businessId}/stockCountResults"
}]
}
[ 500 ]
Internal Server Error - server encountered an error processing request. This should not happen normally, but it is a generic error message, given when no more specific message is suitable.
{
"errors" : [{
"code" : 500,
"message" : "Internal Error",
"description": "The request failed due to an internal error"
}]
}
[ 501 ]
Not implemented - indicates that the server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
{
"errors" : [{
"code" : 501,
"message" : "Not implemented",
"description" : "Operation POST /stockCountResults for Business Id: xxxx not implemented"
}]
}