8 articles about Integration, in reading order.
Integration
Every business application ends up talking to something else: an accounting package calls in, a payment provider gets called out to, files go somewhere other people can fetch them. This is the map of how Parsware does each of those, and of the series that walks through them one at a time.
Integration
A Custom API gives another system one address to call that keeps its shape while your tables change. We built one from nothing: the contract, the script behind it, the OpenAPI description it generates, a call from outside, and a second version answering beside the first.
Integration
A Custom API doesn't have to answer JSON. Declare HTML and its script writes a page: here, a receipt for one booking that another system can drop into a confirmation email or open in a browser. And because the page is built from what a guest typed, every value goes through htmlEncode on its way in.
Integration
Before another system can call Parsware it needs an identity of its own: an app registration, with a client id, a secret, the scopes it may use and the role it holds. We registered a front-desk dashboard that reads visitors and nothing else, and looked at what each of those choices decides.
Integration
A registered application doesn't send its secret with every call. It trades it, once an hour, for an access token, and sends that. Here is the one request that gets one, what is inside it, how to use it, and what each refusal means.
Integration
At the end of the month, finance wants the expense claims as a CSV file it can fetch. A Custom API builds the file from the claims table and puts it in object storage, where it stays until somebody collects it. We called it from finance's own system and found the file in the Storage screen.
Integration
A reporting tool outside Parsware wants your data: which tables it may read, what their columns are, pages of rows, and totals. The reporting endpoints answer exactly that, read-only, and only what the application's role may read. We pointed the front-desk dashboard at them, and ran a saved query by name.
Integration
Every table, view, form, query, report and process you build in Parsware is a plain JSON document underneath, and every kind has a published schema. So a document can be written in an editor, by a script or by an AI assistant, checked before it's sent, and the platform checks it again the same way the designer's own are. We wrote a saved query by hand.
