Fuse5 Authentication, Database Structure & Limits
| Version | Date | Created / Updated | Notes |
|---|---|---|---|
| v1.0 | 03.04.2025 | Bogomil | First publish |
| v1.1 | 28.05.2025 | Danail Deltchev | New table introduced in Fuse5 Connector for Locations management for GetStock |
Authentication
Fuse5 authentication goes through an API key which does not expire. Every client will have different API Key and URL which we will use to make the requests. The actual request structure is really simple and we just need to specify the token and the services: Sample structure:
{
"authenticate":{
"apikey":"API KEY"
},
"services":[
{
"call":"sales_order/get_finalized_date",
"identifier":{
"limit":20,
"offset":0,
"sales_order_finalized_date_start":"YYYY-MM-DD HH:MM:SS",
"sales_order_finalized_date_end":"YYYY-MM-DD HH:MM:SS"
}
}
]
}We will always use the same url and the same API Key for each request with method POST.
The body should be pushed as form-data type in a data variable
Database
Additional tables will need to be created, however please note the structure and names are just suggestions.
Fuse5 Connector - here we will be storing all the Fuse5 details required from the connection to work and this is our starting point. Please note this table should be accessible via the menu under the connector section
| Fields Name | Type | Required | Comment | Default Value |
|---|---|---|---|---|
| Name | varchar | Yes | Field for internal use to differentiate the Fuse5 connectors. | |
| Active | checkbox | Flag indicating if the Fuse5 connector is active and based on this we can switch off and on the connector | false |
|
| URL | varchar | Yes | The Fuse5 API URL | |
| API Key | varchar | Yes | The API Key used for the authentication which is provided by Fuse5 | |
| Create Orders | checkbox | No | false |
|
| Get Shipment | checkbox | No | false |
|
| Get Stock | checkbox | No | false |
|
| Get Price | checkbox | No | false |
|
| SKU Delimiter | varchar | Yes | This will define what delimiter to use for the SKU because we will be generating the SKU from “line_code" and "product_number . This field should not be empty | - |
| Order status for export | dropdown | No | Enumerations: |
Ready For Shipping
Shipped
Both | “Both” |
| Order items for export | dropdown | No | Enumerations:
Bundles
Components
Both | “Both” |
<v1.1>
Fuse5 Connector > Locations Mapping
| Field Name | Type | Required | Comment |
|---|---|---|---|
| Fuse5 Location | dropdown | Yes | Dropdown from Fuse5 downloaded enumeration locations |
| MCP Location | drodown | Yes | Dropdown from all MCP available locations |
Every Fuse5 Connector should be able to hold multiple location mappings which should be unique based on the Fuse 5 location (no reason to have the same connections twice). In other words - we can’t have the same Fuse 5 Location mapped more than once per Fuse 5 Connector
</v1.1>
Channel Fuse5 Connector - dependant table of Channel where there will be a dropdown list with all Fuse5 Connectors.
| Field Name | Type | Required | Comment | Default Value |
|---|---|---|---|---|
| Connector Name | dropdown | Yes | ||
| Fuse5 Account Number | dropdown | Yes | ||
| Get Prices as Original Price | checkbox | No | False |
Limits
There are no limits mentioned by Fuse5.