API Connections
Move data between systems, and prove it arrived.
Connect a source API to a target API, map the fields, and let GridTailor deliver, retry and reconcile. Every record has a trail. Now in design-partner preview.
How it works
-
Connect
Add each system with its own credentials, stored encrypted in AWS Secrets Manager, never in the browser.
-
Map
Map fields with safe, built-in transforms. Each change saves a new, versioned spec with a diff you can review and roll back.
-
Deliver
Records flow through a queue with automatic retries, rate-limit awareness and a dead-letter queue for anything that needs a person.
-
Prove
The ledger reconciles every source record to delivered, in flight, or needs attention, with an audit entry for every change.
What you get
One strong generic REST connector
API key, bearer token and OAuth 2.0 client credentials. It honors Retry-After, backs off with jitter, and warns you before credentials expire.
Per-record ledger
Idempotency keys stop duplicate writes on replay. See exactly which records failed and why.
Versioned integration specs
Integrations are immutable, versioned definitions. You always know who changed what, and when.
Safe by default
HTTPS only, a per-integration host allowlist, and blocked private network addresses. Mappings can't run arbitrary code.
Have an integration that keeps breaking?
Tell us about it. We're onboarding a small number of design partners.