Ellipse Gradient for Header

Unleashed Software Integration Guide

Integrate Unleashed Software with enterprise systems through its signed REST API, paginated resource retrieval, and Martini workflows for synchronization and orchestration.

Unleashed Software integration options at a glance

Unleashed Software provides a documented HTTPS REST API for Products, Customers, Suppliers, Sales Orders, Purchase Orders, Warehouses, and inventory-related resources. Requests use an API ID, API key, and HMAC-based request signature, while collection responses are retrieved through pagination. Broad webhook coverage, bulk or asynchronous APIs, GraphQL, SOAP, file APIs, and direct database access were not confirmed. Martini can consume the REST API in scheduled workflows, maintain pagination checkpoints, map and validate data, apply business rules, and expose normalized APIs to downstream applications. Polling is the preferred synchronization approach where event delivery is unavailable or limited.

Integration pointSupported by Unleashed Software?Common use casesHow Martini supports it
REST APIsYesUnleashed exposes HTTPS resource endpoints for Products, Customers, Suppliers, Sales Orders, Purchase Orders, Warehouses, and inventory-related data. These are the documented approach for application integration.Martini can consume the Unleashed REST API in workflows, transform JSON responses, apply validation and business rules, and expose REST APIs for downstream consumers.
AuthenticationYesRequests use an API ID, API key, and HMAC-based signature supplied with the request. Calls should be made over HTTPS and remain subject to Unleashed account permissions and subscription configuration.Martini can store the API ID and API key as protected configuration values and generate the required signed request parameters in an integration workflow.
PaginationYesCollection retrieval uses documented page and page-size parameters. Pagination is required for larger Product, Customer, order, supplier, and inventory synchronizations.Martini can iterate through pages, persist checkpoints, control request concurrency, and resume a failed synchronization without restarting the full collection.
Scheduled synchronizationYesA scheduled polling design is appropriate where broad webhook or outbound-callback coverage is unavailable or has not been confirmed. Incremental filtering must be verified for each resource.Martini can trigger recurring workflows, retrieve changed or relevant pages, compare synchronization state, and write results to connected applications.
Webhooks / outbound callbacksNot confirmedBroad event delivery for Product, Customer, Sales Order, Purchase Order, or inventory changes was not confirmed. Specific features should be verified before relying on callbacks.Martini can receive webhook-style requests when a documented Unleashed feature provides them, but otherwise can implement scheduled API polling and checkpointing.
Bulk / asynchronous APIsNot confirmedA separate bulk-import, bulk-export, or asynchronous job API was not confirmed. Pagination should not be treated as a bulk API.Martini can implement controlled page processing, throttling, retries, and checkpointing for large synchronizations using the documented REST resources.
File / attachment APIsNot confirmedA dedicated Unleashed file, document, or attachment API was not confirmed. File exchange should be validated against the specific product feature before design.Martini can process files through supported file-oriented workflows when a separate exchange endpoint or agreed file transport is available, but does not assume one exists in Unleashed.
GraphQL and SOAP APIsNot confirmedOfficial GraphQL and SOAP interfaces were not confirmed. The documented integration approach is the Unleashed HTTP API.Martini supports standards-based GraphQL and SOAP consumption generally, but an Unleashed integration should use the REST API unless another interface is documented for the tenant.

How Unleashed Software exposes data and business events

Unleashed Software REST APIs

Unleashed Software provides an HTTPS REST API with resource-oriented endpoints for Products, Customers, Suppliers, Sales Orders, Purchase Orders, Warehouses, and inventory-related information. Collection responses should be retrieved using the documented pagination parameters.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates with the API ID, API key, and generated request signature, calls the required resource endpoint, processes each page, maps the JSON response into a canonical model, and writes or exposes the result for connected applications.

Implementation sequence

Authenticate the request with the API ID and signed parameters
Call the required Unleashed resource endpoint over HTTPS
Retrieve collection pages using the documented page parameters
Map the response into the target application model
Apply validation, business rules, and duplicate checks
Write the result and store the synchronization checkpoint

Scheduled synchronization

Broad Unleashed webhook or outbound-callback coverage was not confirmed, so scheduled API polling is an important integration method for detecting changes. The availability of suitable incremental fields must be checked separately for each resource.

Martini implementation pattern

Martini implementation pattern: a scheduler starts a workflow at an appropriate interval, the workflow retrieves relevant Unleashed pages, compares stable identifiers or supported modification fields with stored state, processes changes, and records the next checkpoint.

Implementation sequence

Start the workflow on a defined schedule
Load the last successful synchronization checkpoint
Retrieve the relevant Unleashed pages
Filter or compare objects using supported incremental fields
Process new and changed objects idempotently
Persist the checkpoint and reconciliation results

Signed API authentication

Unleashed API requests use an API ID, API key, and HMAC-based request signature. OAuth 2.0 and OAuth-style scopes were not confirmed in the reviewed documentation.

Martini implementation pattern

Martini implementation pattern: protected environment values hold the API credentials, while workflow logic constructs the request parameters and signature required by Unleashed. HTTPS is used for transport, and account permissions remain enforced by Unleashed.

Implementation sequence

Store the API ID and API key as protected configuration
Construct the documented request parameters
Generate the HMAC-based request signature
Send the request over HTTPS
Handle authentication failures separately from validation failures
Rotate protected credentials according to operational policy

Common Unleashed Software integration patterns

Pattern 1: Import e-commerce orders into Unleashed Software

When to use this pattern

Use this pattern when Shopify, WooCommerce, or another commerce application is the order-entry system and Unleashed should manage the resulting Sales Orders, Customers, and inventory operations. It is suitable for scheduled retrieval or a documented event-assisted flow.

Integration direction
Shopify or WooCommerce
Martini
Unleashed Software
Example Mapping
Unleashed Software FieldCanonical FieldTarget Field
order numbersourceOrderIdSales Order number
line product codeproductCodeProduct code
customer emailcustomerEmailCustomer email
order total currencycurrencySales Order currency
Martini implementation pattern

Martini retrieves source orders, resolves Product and Customer identifiers, validates tax and currency mappings, checks the source order number before creation, and writes the Sales Order to Unleashed. Temporary API failures are retried, while missing products or ambiguous customers are routed to an exception process.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • error handling
  • scheduled execution

Pattern 2: Publish Unleashed inventory to commerce channels

When to use this pattern

Use this pattern when Unleashed is authoritative for warehouse inventory and Shopify or WooCommerce must display current availability. The design should explicitly define contributing warehouses, safety stock, and the meaning of sellable quantity.

Integration direction
Unleashed Software
Martini
Shopify or WooCommerce
Example Mapping
Unleashed Software FieldCanonical FieldTarget Field
Product codeskuvariant SKU
Stock On HandwarehouseQuantityinventory quantity
warehouselocationCodeinventory location
available quantityavailableToSellavailable inventory
Martini implementation pattern

A scheduled Martini workflow retrieves Warehouses and Stock On Hand in pages, calculates the target available-to-sell value, excludes discontinued or unmapped Products according to business rules, and updates the commerce platform idempotently. The workflow records partial failures for retry and reconciliation.

Martini capabilities used
  • scheduler triggers
  • API consumption
  • data mapping
  • business rules
  • workflow orchestration
  • retry handling

Pattern 3: Synchronize suppliers and purchase orders

When to use this pattern

Use this pattern when Unleashed purchasing data must align with NetSuite, QuickBooks Online, or another procurement or finance application. It supports supplier-master synchronization and controlled exchange of Purchase Orders.

Integration direction
Unleashed Software
Martini
NetSuite or QuickBooks Online
Example Mapping
Unleashed Software FieldCanonical FieldTarget Field
Supplier codesupplierIdvendor identifier
Purchase Order numberpurchaseOrderIdpurchase order number
line product codeproductCodeitem identifier
quantity and unitorderedQuantityquantity and unit of measure
Martini implementation pattern

Martini retrieves Suppliers and Purchase Orders, normalizes supplier identifiers and units of measure, validates product and tax mappings, and sends approved documents to the target application. Permanent validation failures are separated from transient API errors, and source identifiers support replay without duplicates.

Martini capabilities used
  • workflows
  • API consumption
  • data transformation
  • validation
  • business rules
  • error handling

Pattern 4: Synchronize customer and product master data

When to use this pattern

Use this pattern when Unleashed shares Product and Customer master data with a commerce, CRM, or accounting application. The implementation should define field ownership and prevent update loops or conflicting changes.

Integration direction
Unleashed Software
Martini
Salesforce, Shopify, WooCommerce, Xero, or QuickBooks Online
Example Mapping
Unleashed Software FieldCanonical FieldTarget Field
Product codeproductExternalIdexternal product ID
Product descriptionproductNameproduct name
Customer numbercustomerExternalIdaccount external ID
Customer account informationcustomerProfilecustomer or account profile
Martini implementation pattern

A scheduled workflow retrieves paginated Products and Customers, applies system-of-record rules, transforms fields into the target model, and writes only eligible changes. Martini stores checkpoints, validates required identifiers, and sends mismatches to reconciliation rather than silently overwriting authoritative data.

Martini capabilities used
  • scheduled workflows
  • pagination handling
  • mapping and transformation
  • validation
  • checkpointing
  • reconciliation

Applications commonly integrated with Unleashed Software

Unleashed Software can be connected with commerce, accounting, CRM, and ERP applications through its REST API. The exact objects, direction, and system-of-record decisions should be validated against the customer’s Unleashed edition, subscription, and application configuration.

Application Scenario Direction Martini Pattern
Shopify Synchronize storefront orders and customer details into Unleashed while publishing product and inventory availability back to the commerce channel. Shopify → Martini → Unleashed Software A Martini workflow retrieves or receives Shopify order data, matches Product codes and Customers, validates tax and currency fields, and creates idempotent Sales Orders in Unleashed. A separate scheduled workflow retrieves inventory from Unleashed and updates Shopify.
WooCommerce Connect online orders with Unleashed stock and order-management processes and keep product availability aligned across the storefront. WooCommerce → Martini → Unleashed Software Martini polls or consumes the available WooCommerce integration endpoint, maps products and customers to Unleashed identifiers, checks for an existing order reference, and writes Sales Orders. Inventory updates are processed page by page and retried after transient failures.
Xero Align accounting information, customers, products, invoices, payments, and sales operations with inventory activity in Unleashed. Unleashed Software → Martini → Xero Martini retrieves relevant Unleashed Customers, Products, and Sales Orders, transforms them into Xero accounting models, applies tax and account-mapping rules, and records source identifiers for reconciliation and duplicate prevention.
QuickBooks Online Transfer sales and purchasing information into accounting workflows and align customer or product references where the customer configuration requires it. Unleashed Software → Martini → QuickBooks Online A scheduled Martini workflow retrieves approved Unleashed Sales Orders and Purchase Orders, maps customer, product, tax, and currency fields to QuickBooks Online, validates required references, and routes rejected documents for review.
Salesforce Coordinate customer, account, opportunity, order, product, fulfillment, and inventory information between CRM processes and Unleashed operations. Salesforce → Martini → Unleashed Software Martini exposes or consumes APIs for approved Salesforce orders, resolves Product and Customer identifiers in Unleashed, applies approval and duplicate checks, and returns order or inventory status to Salesforce through a reusable workflow or API.
NetSuite Coordinate inventory, purchasing, sales-order, and financial processes between Unleashed and an ERP environment. NetSuite → Martini → Unleashed Software Martini orchestrates scheduled retrieval and write operations, maps Suppliers, Products, Purchase Orders, and Sales Orders between the systems, applies system-of-record rules by object, and stores checkpoints for replay and reconciliation.

How to build a Unleashed Software integration in Martini

Objective

Establish the Unleashed API connection using the documented signed-request mechanism and protect credentials in the Martini environment.

Instructions in Martini

  • Configure the Unleashed API ID as protected configuration
  • Store the API key as a secret
  • Implement the documented HMAC-based request signature
  • Use HTTPS and separate authentication failures from business errors

Objective

Select scheduled polling as the default trigger unless a specific Unleashed feature provides a documented event or callback suitable for the integration.

Instructions in Martini

  • Define the synchronization frequency
  • Verify whether the resource supports suitable incremental filtering
  • Configure a scheduler trigger
  • Document the polling checkpoint and expected processing window

Objective

Read the required Unleashed resources through paginated REST requests without assuming bulk or asynchronous APIs.

Instructions in Martini

  • Call the relevant resource endpoint
  • Process page and page-size parameters
  • Control concurrency and request volume
  • Persist the current page and checkpoint for recovery

Objective

Coordinate retrieval, validation, transformation, target writes, and reconciliation in a maintainable Martini workflow.

Instructions in Martini

  • Separate extraction, mapping, validation, and delivery stages
  • Use conditional routing for valid and invalid objects
  • Store stable source identifiers
  • Create reusable workflow logic for shared API operations

Objective

Convert Unleashed Products, Customers, Suppliers, orders, and inventory into the target application’s data model.

Instructions in Martini

  • Map Product codes and customer or supplier identifiers
  • Normalize tax, currency, units, and warehouse values
  • Apply explicit field ownership rules
  • Validate required fields before writing

Objective

Enforce idempotency, inventory semantics, approvals, and system-of-record decisions before changing either system.

Instructions in Martini

  • Check stable order, product, customer, or supplier identifiers
  • Define available-to-sell and safety-stock calculations
  • Reject ambiguous mappings
  • Prevent update loops between systems

Common Unleashed Software data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
ProductsSynchronize product codes, descriptions, pricing, and inventory-related attributes.Shopify, WooCommerce, Xero, QuickBooks Online, Salesforce, NetSuiteMartini retrieves Products page by page, validates stable product identifiers, applies ownership and field-mapping rules, and prevents duplicate creation in target systems.
CustomersRepresent customer accounts and associated account information for orders, accounting, and customer master-data synchronization.Shopify, WooCommerce, Xero, QuickBooks Online, SalesforceMartini matches Customers using documented identifiers or customer numbers, normalizes contact and address fields, and applies deduplication before writes.
SuppliersSupport purchasing and supply-chain processes involving supplier records and purchase orders.NetSuite, QuickBooks Online, procurement applications, finance applicationsMartini maps supplier codes and account attributes, validates required fields, and routes ambiguous or missing mappings for review.
Sales OrdersCapture customer orders received from commerce, CRM, or other downstream applications.Shopify, WooCommerce, Salesforce, Xero, NetSuiteMartini maps order lines, Product codes, Customers, tax, currency, and source references, then uses idempotency checks before creating or updating orders.
Purchase OrdersRepresent orders placed with Suppliers and coordinate purchasing workflows.NetSuite, QuickBooks Online, procurement and finance applicationsMartini transforms supplier, line-item, unit, tax, and currency data, validates business rules, and records failed identifiers for replay.
Warehouses / Stock On HandProvide warehouse locations and inventory quantities for availability and fulfillment synchronization.Shopify, WooCommerce, Salesforce, NetSuite, reporting applicationsMartini retrieves warehouse-specific inventory, applies safety-stock and available-to-sell rules, and publishes calculated quantities idempotently.

Authentication and security considerations

Signed API authentication

Unleashed Software uses an API ID, API key, and HMAC-based request signature rather than a confirmed OAuth 2.0 flow. API calls should use HTTPS and remain subject to the permissions and subscription configuration of the Unleashed account.

Martini protection

Store the API ID and API key in protected Martini configuration or secrets. Keep signing logic reusable and separate from business mappings, and restrict access to integration assets according to the deployment environment.

  • Do not embed API keys in workflow payloads or source-controlled definitions.
  • Validate authentication failures separately from authorization and data-validation failures.
  • Review credential rotation and tenant permission procedures with the Unleashed administrator.

Operational considerations for Unleashed Software integrations

Pagination and rate control

Process collection endpoints page by page using the documented parameters. Control concurrency and account for quotas, throttling, and transient HTTP failures with appropriate retry and backoff policies.

Idempotency and reconciliation

Use stable identifiers such as order numbers, Product codes, customer numbers, supplier codes, and purchase-order numbers. Persist checkpoints and compare key totals or object counts so failed or partial runs can be reconciled.

Mapping and inventory semantics

Explicitly map product codes, warehouses, units of measure, tax codes, currencies, and customer or supplier identifiers. Define whether the target receives total Stock On Hand, warehouse-specific quantities, or a calculated available-to-sell value.

Change management

Treat API responses as integration contracts. Validate required fields, tolerate nonessential additions where appropriate, and test changes to resource fields, pagination behavior, authentication requirements, and error formats before production deployment.

Why use Martini instead of scripts or point-to-point integrations?

Centralized orchestration

Martini coordinates extraction from Unleashed, transformation, validation, target writes, retries, and reconciliation in workflows rather than scattering logic across independent scripts.

Reusable integration assets

Teams can separate authentication, pagination, mapping, business rules, and delivery into maintainable workflow components and expose normalized APIs to downstream applications when appropriate.

Operational control

  • Use protected configuration for signed API credentials.
  • Maintain checkpoints for scheduled synchronization and recovery.
  • Route validation failures separately from transient API failures.
  • Monitor workflow execution and retain identifiers needed for replay.

This approach reduces duplicated point-to-point logic while preserving the flexibility to implement Unleashed-specific mappings and request-signing behavior.

Frequently asked questions

How can Unleashed Software be integrated with enterprise systems?

Unleashed Software provides a documented HTTPS REST API for Products, Customers, Suppliers, Sales Orders, Purchase Orders, Warehouses, and inventory-related resources. Enterprise integrations typically use API ID and signed API-key authentication, paginated retrieval, and scheduled synchronization. Broad webhook coverage, bulk APIs, GraphQL, SOAP, and direct database access were not confirmed.

Can Martini integrate with Unleashed Software?

Yes. Martini can consume the Unleashed REST API, generate the required signed requests using protected configuration, orchestrate paginated synchronization workflows, transform data, apply business rules, and expose APIs for downstream applications.

Do I need a connector to integrate Unleashed Software with Martini?

No. A dedicated Unleashed Software connector is not required. Martini can integrate using Unleashed’s confirmed REST API, API ID, API key, request-signing mechanism, pagination, and scheduled polling approach.

Is there any extra Lonti cost to integrate Unleashed Software with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Unleashed Software. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Unleashed, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.

Which Unleashed Software integration methods should be used?

The documented and recommended method is the Unleashed HTTPS REST API with API ID, API key, and HMAC-based request signatures. Use pagination for collections and scheduled polling for synchronization unless a specific documented callback is available. GraphQL, SOAP, bulk APIs, and direct database access were not confirmed.

Does Unleashed Software provide webhooks or event notifications?

Broad webhook or outbound-callback coverage for Products, Customers, orders, suppliers, or inventory was not confirmed. A specific feature should be verified before relying on event delivery. Martini can use scheduled API polling and persisted checkpoints where callbacks are unavailable or insufficient.

How does synchronization and data mapping work?

Martini retrieves Unleashed resources page by page, maps them into a canonical or target model, and applies rules for Product codes, customer and supplier identifiers, tax, currency, units, and warehouse quantities. Stable identifiers and stored checkpoints support incremental processing and duplicate prevention.

How are errors, retries, and duplicate records handled?

Martini workflows can separate transient API failures from permanent validation errors, retry temporary failures with controlled backoff, and record failed object identifiers for replay. Idempotency checks based on order numbers, Product codes, customer numbers, supplier codes, or other stable identifiers prevent duplicate creation. Martini can also expose a normalized API façade over the integration, although the underlying Unleashed interface remains REST-based.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect Unleashed Software with Martini

Use Martini to build maintainable Unleashed Software integrations with signed REST API requests, scheduled synchronization, data mapping, validation, and workflow-based orchestration.

EXPLORE MARTINI
BOOK A DEMO