Import data

For anything recurring, data is onboarded by a data provider — a custom integration that calls the ingest API. The provider is where system-specific business logic lives: reading from the source system, mapping fields, and pushing entries to Occtoo.

​

What you need

1. A source to write into — see Create a source.
2. A data provider that lists that source under Allowed Sources — see Add a data provider.
3. The provider’s ID and secret, used to get a token.

The provider ID is shown on the provider in the Data providers tab. The secret is only shown once, when the provider is created or its secret is reset — see Reset a provider secret.

​

What arrives in the source

Entries are written by key. An entry whose key already exists in the source is updated; a new key creates a new entry. Each property carries an ID, a value and, for localized properties, a language code. Properties the source has not seen before are created automatically. Occtoo infers a type, which you can then correct, along with capabilities and the display section — see Add or edit a property.

​

Watching a run

After an ingest run, the source page shows what happened:

• Updates over time breaks the run into added, updated, deleted and ignored entries, and reports the request rate — see Monitor onboarding.
• The freshness badge in the header moves back to Fresh.
• An entry’s Changelog attributes each change to the provider that made it.

​

Reference

• Get data into Occtoo — the quick start, end to end.
• Ingest API overview — endpoints and payload shape.
• Application token — getting a token from a provider ID and secret.
• Integrations — ready-made providers for common systems.

​

Without an integration

For a one-off load, or while you are still modelling the data, upload a CSV in Studio instead: Import data from a CSV file. No data provider is needed for that route.