Version: Next (unreleased)

Changelog

Notable changes to the Datamingle API. Entries are dated in YYYY-MM-DD and grouped by date.

2026-04-17

Pass-through API keys. API keys no longer require a linked integration partner. A key with only scopes can call every endpoint directly against the internal schema — no field mapping applied. See Pass-through keys.
Inventory by SKU. GET /inventory/{identifier}/?by=sku returns every location holding the SKU. ?by=location (default) keeps the previous behavior. Response shape is now uniform across both modes: {location_code, sku_code, quantity}. See Inventory.
Cursor pagination on all list endpoints (orders, inventory, locations, products). Accepts ?limit= (1–200, default 50) and ?cursor=. Responses include a new top-level pagination object. See Pagination.

Identifier field resolution now falls through safely. Products and locations now honor the partner's default_identifier_field like orders already did. If the configured field doesn't exist on the resource model (e.g. a partner configured for external_order_id addressing products), the platform falls back to the resource default (sku, code) instead of erroring. See Identifiers — Resolution order.
Error code casing normalized to UPPER_SNAKE_CASE across all responses. validation_error → VALIDATION_ERROR.
MAPPING_ERROR now returns 422 Unprocessable Entity instead of 400.
Scope segment for inventory is integrations.inventory.* (was inventorys).

IntegrationLog now records api_key alongside partner, so pass-through traffic is attributable. The partner column is empty for pass-through requests.

Integration endpoints for Products — full CRUD via /api/integrations/v1/products/.
is_active field on Locations exposed via PUT /locations/{code}/.
Bulk activate/deactivate support for SKUs internally (available via dashboard).

DELETE /orders/{identifier}/ now correctly returns 400 SERVICE_ERROR (instead of 500) when the order is already shipped.

Datamingle API v1 general availability.
- Orders, Inventory, Locations endpoints.
- Field mapping engine (rename, dot-path, array index, array-to-array, static values).
- API key scopes with wildcard hierarchy.
- Integration audit log.
Partner templates shipped: Acumatica, SAP Business One, Shopify.

Bookmark /changelog.
For breaking-change notice, rely on the Sunset / Deprecation response headers — see Versioning.

If behavior changes and you can't find it here, open a support ticket with: