Quickstart
POST a file to /v1/uploads with a bearer token and a template ID. The response carries the mapped headers and validation counts; pull rows with GET /v1/uploads/{id}/rows or ship them with POST /v1/uploads/{id}/commit.
curl -X POST https://api.adaptivmapr.com/v1/uploads \
-H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
-F "file=@customers.csv" \
-F "template=users_v1"
Three surfaces
- REST API — for server-side imports. Overview →
- Workbench — hosted UI for one-off ingestion and template authoring. Open the Workbench →
- MCP server — drop AdaptivMapr into Cursor or Claude Desktop. MCP install →
Templates
Twenty-three production-tested schemas — ten healthcare (FHIR-aware) plus Core, CRM, and E-commerce. Browse the catalogue →
Authentication
All API requests carry a bearer token in the Authorization header. API keys are HMAC-signed self-contained credentials — there is no shared session store. Revocation is enforced by a server-side deny-list checked on every request. Mint and rotate keys in the dashboard.
Webhooks
Commit delivers validated rows to your endpoint with an X-AdaptivMapr-Signature header — HMAC-SHA256 over the raw body, signed with the webhook secret you set in the dashboard. Reject any request where the signature does not match; replay protection is enforced with a timestamp prefix.