API Connections
Part of the MountDev Ops Workspace documentation. Updated October 7, 2026
MountDev Ops Workspace documentation | Updated October 7, 2026
The API connections your company uses, in one place. Any service with an API can be added: its address, how it signs in, and its key or token. This page is confidential: only owners and admins see it, and AI agents never do.
What Each Connection Shows
- Its name and what it is for.
- Its address (always https).
- Whether it is working: Working, Failing with the reason, or Not checked yet, and when it was last checked.
A saved key or token is never shown again, to anyone. It is stored encrypted with a key that only your company's workspace can use, and it can only be replaced.
Adding or Changing a Connection
In Setup, API Connections (owners and admins):
- Add a Connection (action
core.connections.save): a name, what it is for, the address, and how it signs in: a bearer token, a key in a header (name the header), a user name and password, a key in the address (name the parameter), or no sign-in. Add a check address, like /v1/status, for the check to ask. - Change a connection the same way. Leave the key empty to keep the saved one. Changing the address, the sign-in, or the key marks it as not checked yet.
- Delete a connection (action
core.connections.delete). - Check Now (action
core.connections.check) asks the service once with the saved key and records whether it answered. - Seeing the list (action
core.connections.list) never includes a key.
