The Fusebit HTTP API managed and executed everything on the platform across two concurrent major versions on one host. v1 (Core, 49 operations) covered accounts, subscriptions, boundaries, serverless functions, users, machine clients, trusted JWT issuers, subscription storage and a private npm registry. v2 (Integrations, 40 operations) covered integrations, third-party credential connectors, per-customer installs and identities, configuration sessions and entity tags. Authentication was a bearer JWT minted against an issuer registered on the account, with authorization expressed as explicit {action, resource} grants rather than OAuth scopes. The API is retired — api.us-west-1.on.fusebit.io no longer resolves in DNS.
Fusebit HTTP API is published by Fusebit on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Developer Tools, Embedded iPaaS, Integration, and Serverless. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.
This API exposes
49 operations
across 33 paths,
organized into 9 resource areas,
and defines 50 schemas.
It is described by OpenAPI 3.0.0, at version 1.0.0.
Requests are made against a single base URL, https://api.{region}.on.fusebit.io.
49 operations33 paths50 schemas6 DELETE25 GET4 PATCH11 POST3 PUT
Metadata
The identity and technical contract details declared by the specification.
Fusebit HTTP API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (AccessToken).
By default, every request must be authenticated.
AccessToken — For a description of the access token format, see [this doc](../../integrator-guide/authz-model).
Paths & Operations 49
Across 33 paths, the API surfaces 49 operations — 6 DELETE, 25 GET, 4 PATCH, 11 POST, 3 PUT. They span 9 resource areas: Accounts, Subscriptions, Boundaries, Functions, Issuers, Clients, Users, Registry, Storage. Each is listed below with its method, path, parameters, and response codes.
The contract defines 50 schemas that model the data the API accepts and returns. The most detailed are NewFunction (12 properties), AccountAuditEntry (7 properties), NewLogQuery (5 properties), NewUser (5 properties). Each schema is shown below with its type and property counts.
Error
object
3 properties3 required
AccountId
string
Account id
QueryId
string
Log Query id
Account
object
3 properties1 required
AccountPatch
object
1 property1 required
AccountAudit
object
2 properties1 required
AccountAuditEntry
object
7 properties7 required
SubscriptionId
string
Subscription id
Subscription
object
2 properties1 required
SubscriptionList
object
2 properties1 required
PublicKey
object
A key id and the public key for a public/private key pair
2 properties2 required
IssuerId
string
Issuer id
NewIssuer
object
An issuer of access tokens that should be accepted
3 properties
Issuer
IssuerList
object
2 properties1 required
InitProtocol
string
The initialization token protocol that determines the type of the source of trust for validating access tokens the user or client will present when making HTTP…
InitRequest
object
2 properties2 required
InitResponse
string
A single-use initialization token in JWT format. If unused, the token expires in eight hours. The profile parameter of the JWT payload contains the information…
InitResolveRequest
object
3 properties2 required
Identity
object
2 properties2 required
AccessStatement
object
2 properties2 required
ClientId
string
Client id
NewClient
object
3 properties
Client
ClientList
object
2 properties1 required
UserId
string
User id
NewUser
object
5 properties
User
UserList
object
2 properties1 required
BoundaryId
string
Boundary id
FunctionId
string
Function id
FunctionLocation
object
1 property1 required
FunctionShort
object
5 properties4 required
FunctionRuntime
object
1 property1 required
Function
FunctionSecurity
object
Properties that impact the runtime security of the function.
3 properties
FunctionRoutes
array
Properties that control route-specific behaviors of the function
NewFunction
object
12 properties
FunctionList
object
2 properties1 required
BuildId
string
Build id
Build
NewLogQuery
object
5 properties
NewLogQueryResponse
object
1 property
LogQueryResult
object
3 properties
RegistryGet
object
2 properties
RegistryPut
object
1 property
StorageId
string
Storage id
StorageShort
object
4 properties1 required
StorageList
object
2 properties1 required
StorageData
object
4 properties
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Fusebit HTTP API, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.
