Sign-in & API Keys
← Setup · Let people sign in with Google, Microsoft, Facebook or your company's login, and give other systems a key to call the API. Either way, what they may do is still set by a role.
A person who signs in this way becomes the Foundation user with the same email address
(Setup → Users & Security → Manage Users), with that user's role. After the first time, the
provider account stays linked to the user (shown on Edit User).
The buttons show on the login page once the site has user logins.
localhost may use http). Use the address users reach the site by.
Google Cloud Console → APIs & Services → Credentials → Create OAuth client ID (Web application). Open
Microsoft Entra → App registrations → New registration (Web). Client id = Application (client) ID; secret from Certificates & secrets. Open
Meta for Developers → Create app → Facebook Login. Client id = App ID, secret = App Secret. Open
Any OpenID Connect provider: Okta, Auth0, Keycloak, Entra ID for one organisation, Google Workspace… Register a web app with the redirect URI below.
For other systems (ERP, accounting, dispatch) calling the API without signing in. Send the key as
X-Api-Key: fdn_… or Authorization: Bearer fdn_….
A key acts with its role: User reads, Manager can also add and change
data through the Integration API, Admin can reach everything an admin can.
Keys work on /api/… only, and can't manage keys or sign-in.
/api/tables then answers only a valid key (or a signed-in user) -
even while the site runs without login. The office's own screens don't use it, so nothing here changes for them.
With login on, every other API call already needs a sign-in or a key.
| Name | Key | Role | Last used | |
|---|---|---|---|---|
| No keys yet. | ||||