Communication Format
Identification & Protocol
The Rekonect API communicates through secure HTTP POST requests over HTTPS. Each client receives a unique API key upon registration, which must be included in the headers of every request to ensure authentication.
Encryption
TLS version 1.2 or above is required to interact with the API securely. Older versions (TLS 1.0 and 1.1) are deprecated due to known vulnerabilities and should not be used.
Rekonect API Servers
Host: https://api.prod.bcomo.com
Note: When a static IP is required, please contact our integration team at pos@comosense.com.
Request Format
The POST body must be a UTF-8 encoded JSON object. The URL for the request should be structured as follows:
https://api.prod.bcomo.com/api/v4/apiCall?apiCallParameters
| Component | Description |
|---|---|
| API server host | The base domain of the API |
| Prefix path + call | API version path and the specific API call name |
| Query parameters | Optional parameters relevant to the API call |
Request Headers
| Header | Description | Type | Required |
|---|---|---|---|
Content-Type | The request payload content type (application/json) | String | Yes |
X-Api-Key | API key used for authentication | String | Yes |
X-Branch-Id | Business branch identifier | String | Yes |
X-Pos-Id | POS terminal identifier that initiated the request | String | Yes |
X-Source-Type | Origin of transaction (e.g., POS, Website, Kiosk) | String | Yes |
X-Source-Name | Name of the integration source (e.g., POS system name) | String | Yes |
X-Source-Version | Version of the integration client or system | String | Yes |
Response Format
The API returns a JSON response object. The status field indicates whether the request succeeded (ok) or failed (error). If an error occurs, the response will include an errors array with detailed diagnostic information.
Error Response Fields
| Field | Description | Type | Always Returned |
|---|---|---|---|
code | Unique error code | String | Yes |
message | Description of the error | String | Yes |
cause | Additional context about the error | Object | Sometimes |
Example Error Response
{
"status": "error",
"errors": [
{
"code": "4001012",
"message": "Customer(s) not found"
}
]
}