The Workspace API is the technical foundation of every connection to snori. Whether it is an automation service, your own script or another program: they all talk to your workspace through the same REST interface. It turns snori into a hub – data flows in under control and just as controlled back out.
What is the Workspace API?
An API is a programming interface: a fixed, documented language in which two systems talk to each other. The snori Workspace API follows the REST principle, the most common standard on the web. A program calls an address (an endpoint), sends or fetches data and gets a clear answer back – usually in JSON format, which every modern tool understands.
The endpoints mirror what you already use in snori: creating and reading pages, writing rows into smart tables, searching or updating entries. Instead of addressing humans, the API addresses machines – yet it works on the same content and under the same rules as the interface. Everything that happens through the API is versioned and can be traced back. Because the API is included in the plan, the interface itself costs you nothing extra.
snori and the Workspace API: the two directions
Every connection has a direction, and the API handles both – often at the same time.
snori as the target – data comes in
Another system sends a record to an endpoint, and snori turns it into a new table row or a new page. This way leads, orders or measurements gather automatically in your workspace, structured and in one place.
snori as the source – data goes out
A program reads your tables and pages through the API and passes them onward: into a CRM, into a data warehouse, into a report. snori becomes the central point of truth that your other tools draw from.
How to set up the connection
- In snori, open the settings for the Workspace API and create an access key (API key) for this specific workspace.
- You decide what that key may do: read only, append, change or also delete.
- In your program you place the key in the request header and call the matching endpoint.
- Done: from now on the data flows in the direction and to the extent you defined.
No intermediary service is needed – if you develop yourself, you talk to the API directly. Automation services use the same interface in the background.
Who can access your data
This is the heart of it. An access key in snori can never do more than you allow. The rights matrix is simple and clear-cut: per key you decide separately about read, append, change and delete – and which single workspace it reaches at all. A key for an import service gets only "append", for example, a reporting script only "read".
Every key applies to exactly one workspace and never silently takes on more. Everything the key does is versioned and can be rolled back. If you no longer need an access point, you revoke the key and the connection is dead at once. Your content stays encrypted throughout in a German data centre certified to ISO 27001.
API, automation or AI – when to use what?
The Workspace API is the shared basis. If you program yourself or connect an existing system, you talk to it directly. If you want to work without code, you place an automation service like Zapier in between, which uses the API in the background. If snori should actively report events outward instead of waiting for queries, webhooks are the right way. And if an AI like ChatGPT or Claude should read and write, the AI connection takes over – always under the same rights as an API key.