Developer PlatformModule 2310 apps
Let other software talk to this one — and build on it Coming by Holi
One decision, not twenty-five: whether anything outside this system may call it. Twenty-five lines of the specification are that single capability written out from four different places, which is why it stands as a module instead of a feature buried in Platform. A versioned surface with keys and rate limits, webhooks going out, functions running on top, and only then a builder that lets somebody assemble a screen without writing code. The order matters, because a builder over nothing is a demonstration. The sign-on model has to be settled before any of it: changing how a caller proves who it is afterwards means reissuing every credential ever handed out.
Part of Platform & Insight
10 apps in Developer Platform
API & Access Keys
A versioned surface over the records this system already keeps, with a key per caller, a rate limit per key, and a log of what each one asked for. Versioned from the first release rather than the third, because the moment an outside system depends on a response shape, changing it silently breaks somebody else’s software at a time nobody chose. A key is scoped to exactly the records its holder may already read, so this can never become a way around the permissions every screen obeys.
Webhooks
The other direction: this system calling out when something happens rather than waiting to be asked. A subscription names the event and the address to post to, deliveries are signed so the receiver can tell a real call from a forged one, and a failed delivery is retried on a widening interval and then parked where somebody can see it instead of being dropped. Every attempt is recorded, because an integration that silently stopped firing is worse than one that never worked at all.
Functions & Scripting
Small pieces of logic that run inside the system — when a record changes, on a schedule, or when an automation calls them. Each runs with a time limit, a memory limit and the permissions of whoever or whatever triggered it, so a script can never read what its author could not. What a function did lands in the same audit trail as everything else.
Low-code App Builder
Assemble a screen and the record behind it by dragging fields rather than writing code, for the cases a trade needs and nobody anticipated. What it produces is a configuration row, exactly as an industry pack is, and never a separate copy of the software — so an assembled screen still obeys company scoping, the audit trail and every guarantee the rest of the system makes.
Builder Data Model
The tables and relationships a built application stands on: what a record is, which other records it points at, and which fields may not be empty. Kept separate from the builder because the data model is the expensive half to change later — a screen can be redrawn in an afternoon, a relationship that was wrong has to be migrated with all the rows already sitting in it.
App Versioning & Release
A built application has versions, somewhere to try one before it goes live, and a way back. Without this the person who assembled a screen is editing the live system at the exact moment they are still learning it, which is how a business loses a day of entries.
Developer Console
One place to see what the platform is doing for a given caller: keys issued, calls made, webhooks delivered or failed, functions run, and what each one cost. Somebody debugging an integration at two in the morning should not have to ask a person for a log.
App Marketplace
A directory of applications built on this platform that a business can install into its own company, with what each one may read and write shown before installation rather than discovered after it. Nothing installs without somebody first seeing the scope it is asking for.
Robotic Process Automation
Driving another system that offers no interface of its own by working its screens the way a person would. It is the least reliable way to connect anything, and worth having only when the alternative is somebody retyping figures every morning — so it is recorded here as a last resort with a run log proving what it actually did, never presented as equivalent to a real connection.
AI App Builder
Describe a small app in plain words — the records it keeps, the screens it needs, the rules it follows — and the AI builds it on the Builder’s data model, tests it and shows the result. Nothing goes live until a person approves it.