What is deprecated
Media ingest (
/media/* endpoints) is not affected by this announcement and continues to use the Data Provider access token.
ingest.occtoo.com domain
The ingest.occtoo.com domain is deprecated. It covers the Data Provider token, the legacy import, and media ingest under /media. Only the domain is deprecated; media ingest itself stays.
- New development: use
https://api.occtoo.comonly. All endpoints in the Ingest API reference are served there. - Existing integrations: calls to
ingest.occtoo.comkeep working for now. Move them toapi.occtoo.comwhen you migrate to typed source ingest.
Why
The legacy import accepts every value as a string and leaves type handling to downstream configuration. Typed source ingest validates each value against the property type configured on the source — numbers are numbers, booleans are booleans, lists are arrays — so invalid data is rejected at import time with a clear error instead of surfacing later as a broken card or destination. It also uses the same tenant-level Application identity as the Events and Configuration APIs, replacing per-Data-Provider credentials.What changes
Migration steps
1
Create an Application
In Occtoo Studio, create a tenant-level Application with the
write:sources scope and grant it access to the sources you import into. Note the client ID, client secret, and your Tenant ID. See Applications.2
Set property types on your sources
Typed ingest validates values against the property types configured on the source. Review each source’s properties in Studio and set the correct type and, for list types, the delimiter. See Source properties. Properties you do not configure are inferred from the first value received; new list properties default to the
, delimiter.3
Switch your client
Use the .NET SDK or call the typed endpoint directly.
- .NET SDK
- HTTP
Replace Before, with the legacy import:After, with typed source ingest:
Occtoo.Onboarding.Sdk with Occtoo.Sdk:SourceEntry.Delete(id) replaces Delete = true on a DynamicEntity; it carries no properties and can share a batch with upserts. The SDK acquires, caches, and refreshes the token for you, retries 429 and 5xx responses honoring Retry-After, and returns validation failures as values rather than exceptions. See the SDK repository for the full guide.4
Review delete handling
Deletes work the same way: set
"delete": true on the entry and send no properties. The legacy "properties": [] on a deleted entity can stay or be omitted. A delete that also sends properties is rejected with 400.5
Verify and decommission
Run both integrations in parallel if needed, confirm entries arrive with the expected types in Studio, then switch traffic to typed ingest and remove the Data Provider credentials from Studio if nothing else uses them.
Timeline
Questions about your migration? Contact your Occtoo representative.