Third-party apps
Third-party apps lets a developer register an app on a Startup’s API, which each Customer’s admin authorizes for its Tenant, with Verbs as its scopes.
Contract
Status planned. A developer registers an app once, naming the Verbs it needs.
A Customer's admin approves them for its own Tenant on the Startup's Domain. The app receives a token that reaches that Tenant only.
Each Action the app takes records the app as by and the Customer as for. The admin revokes the grant in the Portal, and the next call fails with 401. No screen names the platform: the consent page carries the Startup's Brand.
A Customer can give an outside tool its own key from the Portal, scoped to the Verbs that tool needs.
Verbs
None.
Interfaces
None.
Example
A property-software vendor registers an app that reads renewals from Leaseline. Harbor Residential's admin approves Lease.list and Lease.get for its Tenant, and the app syncs Harbor Residential's leases each night.