API Resources
Define an external HTTP API once — base URL, authentication, and headers — and reuse it everywhere: Quick Calls, MOP steps, and AI tools. Supports Basic, Bearer, API-key, custom-header, and multi-step auth flows, with a built-in test.
Overview
An API Resource is a reusable, centrally managed definition of an external HTTP API: its base URL, how to authenticate, and any standing headers. Instead of re-entering credentials in every Quick Call, MOP step, or AI tool, you define the resource once and reference it.
Authentication Types
API Resources cover the auth schemes real systems use:
- Basic — username/password.
- Bearer — a token in the
Authorizationheader. - API key — key in a header or query parameter.
- Custom header — arbitrary header(s) you specify.
- Multi-step — an auth flow that first calls a token endpoint, then uses the result on subsequent requests.
Secrets in an API Resource are stored locally with your other credentials — see Credentials: Vault.
Testing a Resource
Each resource has a built-in test: NetStacks issues a request to a configurable test path and shows you the exact URL it called and the headers it sent (with secrets redacted), so you can confirm auth works before wiring the resource into automation. Multi-step flows can be tested step by step.
Q&A
- Q: Why centralize APIs instead of per-call config?
- A: One definition means one place to rotate a token, one place to fix a base URL, and consistent auth across Quick Calls, MOP steps, and AI tools.
- Q: Are credentials shown back after I save them?
- A: No. The test view redacts secrets; stored secrets are not echoed in responses.