Skip to main content
Version: 1.0

Custom Integrations

You only need this section if your external system sends data in its own shape — for example, an Acumatica ERP that emits OrderNbr instead of order_number, or a Shopify store that wraps line items in line_items instead of items.

If you can adapt your payload to Datamingle's default shape, you don't need any of this. Stop here.

What customization gives you​

  • Your field names, our validation. Send po_number, we route it to order_number internally. Validation errors and responses come back in your terms — your integration code never learns our names.
  • One template, done. Partner templates (Acumatica, SAP, Shopify, …) ship with a mapping that already works for the standard install of those systems. Pick one and stop.
  • Your identifier, in URLs. Address records by po_number, external_ref, or whatever your system uses — no translation layer needed.
  • Full audit trail. Every inbound request is stored with raw and mapped payloads side by side, so you can diff what you sent against what we interpreted.

How it works at a glance​

Your payload (your field names)
        │
        ▼
Mapping engine  ──►  Internal format  ──►  Validation & persistence
                                                   │
Response (your field names) ◄──────── Reverse mapping

Everything is configured in the dashboard — nothing to deploy on your side.

Where to start​

  1. Partner templates — browse what ships out of the box.
  2. Field mapping — the capabilities of the mapping engine.
  3. Configuring mappings — the dashboard workflow.
  4. Identifiers — address records by your own IDs.
  5. Integration logs — inspect raw vs. mapped payloads while you build.