Capability · Layouts

Reuse last mapping, and catch drift.

Every confirmed mapping is cached by a fingerprint of its header row, so a recurring import is one-click reuse with zero AI. The same fingerprint detects schema drift before it breaks your pipeline.

Get an API key Read the docs

POST /v1/layouts/lookup

What you get

Built for regulated workloads

The same file lands every week. There’s no reason to re-run the cascade — let alone the AI — when the header row is identical to one you’ve already confirmed. AdaptivMapr fingerprints every confirmed mapping with a SHA-256 hash of its normalized header row, so a repeat import is one-click “reuse last mapping” with zero AI. The very same fingerprint powers deterministic schema-drift detection: when a known source shows up with a new field set, you hear about it before the pipeline breaks.

Reuse

One-click, zero AI

A confirmed header→field mapping is stored against a SHA-256 fingerprint of its normalized header row. When the same header row returns, /v1/layouts/lookup offers the stored mapping instantly — no cascade, no LLM, no token cost (just the small flat per-map fee).

Drift

Catch schema changes early

/v1/layouts/drift compares a new field set for a known source against the newest confirmed layout and returns stable, first_seen or drift — with an added / removed / common diff and a reordered_only flag. Deterministic, no LLM.

Scoped

Workspace-scoped, no leakage

Layouts are scoped to your workspace — there’s no cross-tenant sharing of your header fingerprints or mappings. Reuse only ever offers mappings you confirmed.

Automatic

Recorded on commit

You don’t curate a library by hand — commit records the layout automatically, and /v1/layouts/record exposes the same write. Every confirmation quietly makes the next identical import a one-click, zero-AI reuse.

Try it

A real call, end to end

Fingerprint the header row on lookup to reuse a confirmed mapping, or on drift to compare against the last known layout for a source.

Good to know

The fingerprint is a SHA-256 of the normalized header row — order-insensitive enough to flag pure reorders via reordered_only.
Both reuse and drift are deterministic and call no LLM — they add no token cost on every import.
Layouts are workspace-scoped; there is no cross-tenant sharing.

curl

# reuse — does this exact header row already have a confirmed mapping?
curl https://api.adaptivmapr.com/v1/layouts/lookup \
  -H "Authorization: Bearer $MAPR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "headers": ["MRN", "Given", "Surname", "DOB"] }'

# drift — has the field set for this known source changed?
curl https://api.adaptivmapr.com/v1/layouts/drift \
  -H "Authorization: Bearer $MAPR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "template": "patient_demographics",
        "headers": ["MRN", "Given", "Surname", "DOB", "Gender"] }'

response

# lookup → the stored mapping, reusable with one click
{ "match": true, "fingerprint": "b91c…", "mapping": [ … ] }

# drift → a new field appeared since the last confirmed layout
{ "status": "drift",
  "added": ["Gender"], "removed": [], "common": ["MRN","Given","Surname","DOB"],
  "reordered_only": false }

FAQ

Common questions

It fingerprints the normalized header row with SHA-256. If a new upload’s header row hashes to a fingerprint you’ve already confirmed, the stored mapping is offered for one-click reuse — no cascade run, and no AI cost.

A status of stable, first_seen or drift for a known (workspace, template) pair, plus an added / removed / common field diff versus the newest confirmed layout and a reordered_only flag. It’s deterministic and uses no LLM, so you can run it on every import as a guardrail.

No token cost. Reuse and drift are pure fingerprint lookups against your confirmed layouts — no cascade, no embeddings, no LLM. A re-map still draws the small flat per-map fee from your wallet, but nothing token-metered — the whole point is to make a recurring import instant and cheap.

No. Layouts are workspace-scoped, so your header fingerprints and confirmed mappings are never shared across tenants. Reuse only surfaces mappings your own workspace confirmed.

Schema mapping Connectors & webhooks Structural reshape

Ready when you are

Put layout reuse & drift in production — without shipping raw records.

Spin up a key in minutes. Top up a $10 prepaid wallet — every map is a few tokens.

Get an API key See pricing →

$10 minimum to start · pay only for what you map · PHI under BAA coverage