Talk to your AI agent to run Simetrik. →
SimetrikDocs

JaaS

Send files from your own systems into Simetrik and have them land in the source that reconciliation reads — in bulk, or one notification at a time.

JaaS is the ingestion layer of Simetrik. Your systems produce files; JaaS captures them, normalizes them and delivers them to the source your reconciliations read from. You never upload anything through the interface, and nobody has to remember to do it by hand.

You set it up once through the API — one call creates the source — and from then on files arrive through one of two flows. They share the same setup, the same authentication and the same status notifications — with one exception, the inbound webhook call — and what changes is who moves the bytes.

The two flows

File ingestionWebhook flow
What you sendOne JSON record per callA JSON notification pointing at a file
Who moves the fileSimetrik builds it from your recordsSimetrik downloads it from your URL
ConversionJSON → CSV, using the source's column mappingNone — the file is delivered as you published it
TimingRecords are batched, so near-real-timeImmediate, once per notification
Setup callPOST /api/v2/sourcesPOST /api/v2/webhooks
Data callPOST /api/v2/sources/{id}/feed-sourcePOST /api/v2/webhooks/{webhook_id}/feed-source
Best whenYour system emits events or rows continuouslyYou already produce files and publish them somewhere

Nothing stops you from using both in the same workspace — a different source for each is the usual shape.

What stays the same

Whichever flow you pick:

  • Authentication is identical — one credential, the same headers — except for the inbound webhook call, where the webhook_id in the path is the credential. See Authentication.
  • A source is a source. Reconciliation doesn't know or care how the file arrived.
  • You can be notified back. Register a notification_config and Simetrik calls your endpoint as the file moves through the pipeline — including when it fails. See Status notifications.
  • Every call gives you a reference to trace it by — a track id you choose in the webhook flow, an id Simetrik returns in file ingestion.

Start here

On this page