How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
1Fort

1Fort Broker API

**Access:** mixed; some endpoints are public, others require JWT (per endpoint).

Documentation Provider Profile APIs.io OpenAPI GitHub

1Fort Broker API is one of 89 APIs that 1Fort publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Brokers. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, authentication docs, and rate-limit docs.

This API exposes 27 operations across 16 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.1fort.com/apis/.

27 operations 16 paths 17 schemas 3 DELETE11 GET3 PATCH8 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.1fort.com/apis/
Authentication
API Key, API Key
License
Privately owned
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

1Fort Broker API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (Bearer). An API key is passed in the header as Authorization (ApiKey). By default, every request must be authenticated.

  • Bearer — JWT access token. Send as Bearer or JWT .
  • ApiKey — API key. Send as Api-Key .

Paths & Operations 27

Across 16 paths, the API surfaces 27 operations — 3 DELETE, 11 GET, 3 PATCH, 8 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

broker 27

Access: mixed; some endpoints are public, others require JWT (per endpoint).

GET
/broker
List Brokers
broker_list 4 params → 200403500
POST
/broker
Create Broker
broker_create body → 201400403500
POST
/broker/{broker_pk}/accept-invite
Accept Invite
broker_accept-invite_create 1 param body → 201400403500
GET
/broker/{broker_pk}/clients
List Broker Clients
broker_clients_list 5 params → 200403500
POST
/broker/{broker_pk}/clients
Create Broker Client
broker_clients_create 1 param body → 201400403500
GET
/broker/{broker_pk}/clients/{client_pk}/invites
List Broker Client Invites
broker_clients_invites_list 6 params → 200403500
POST
/broker/{broker_pk}/clients/{client_pk}/invites
Invite Client
broker_clients_invites_create 2 params body → 201400403500
POST
/broker/{broker_pk}/clients/{client_pk}/invites/cancel-invite
Cancel Broker Client Invite
broker_clients_invites_cancel_invite 2 params → 201403500
POST
/broker/{broker_pk}/clients/{client_pk}/invites/resend-invite
Resend Broker Client Invite
broker_clients_invites_resend_invite 2 params → 201403500
GET
/broker/{broker_pk}/clients/{id}
Get Broker Client details
broker_clients_read 2 params → 200403404500
PATCH
/broker/{broker_pk}/clients/{id}
Update Broker Client
broker_clients_partial_update 2 params body → 200400403404500
DELETE
/broker/{broker_pk}/clients/{id}
Delete Broker Client
broker_clients_delete 2 params → 204403404500
GET
/broker/{broker_pk}/files
List Broker Files
broker_files_list 11 params → 200403500
GET
/broker/{broker_pk}/invites
List Broker User Invites
broker_invites_list 5 params → 200403500
POST
/broker/{broker_pk}/invites
Invite Broker User
broker_invites_create 1 param body → 201400403500
PUT
/broker/{broker_pk}/invites/{id}
Update Broker User Invite
broker_invites_update 2 params body → 200400403404500
PATCH
/broker/{broker_pk}/invites/{id}
Partially Update Broker User Invite
broker_invites_partial_update 2 params body → 200400403404500
DELETE
/broker/{broker_pk}/invites/{id}
Delete Broker User Invite
broker_invites_delete 2 params → 204403404500
GET
/broker/{broker_pk}/notification-emails
List Sent Notification Emails
broker_notification-emails_list 5 params → 200403500
GET
/broker/{broker_pk}/received-notification-emails
List Received Notification Emails
broker_received-notification-emails_list 5 params → 200403500
POST
/broker/{broker_pk}/received-notification-emails/{id}/mark-as-read
Mark Notification as Read
broker_received-notification-emails_mark_as_read 2 params body → 200404400403500
GET
/broker/{broker_pk}/users
List Broker users
broker_users_list 5 params → 200403500
GET
/broker/{broker_pk}/users/{id}
Retrieve Broker user
broker_users_read 2 params → 200403404500
PUT
/broker/{broker_pk}/users/{id}
Update Broker user
broker_users_update 2 params body → 200400403404500
DELETE
/broker/{broker_pk}/users/{id}
Delete Broker user
broker_users_delete 2 params → 204403404500
GET
/broker/{id}
Get Broker
broker_read 1 param → 200403404500
PATCH
/broker/{id}
Update Broker
broker_partial_update 1 param body → 200400403404500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are BrokerClient (147 properties), BrokerAgencyDetail (59 properties), BrokerAgency (58 properties), BrokerUser (21 properties). Each schema is shown below with its type and property counts.

UserForBrokerAgency
object
3 properties
ValidationError
object
1 property
BrokerAgencyDetail
object
59 properties
BrokerReceivedNotificationEmail
object
11 properties
BrokerNotificationEmail
object
10 properties
BrokerClient
object
147 properties 1 required
BrokerUser
object
21 properties 2 required
BrokerAgency
object
58 properties 2 required
BusinessSubsidiary
object
5 properties 2 required
ApplicationPrefilledForm
object
7 properties 1 required
BrokerUserInvite
object
9 properties 1 required
BrokerFile
object
12 properties 12 required
APIException
object
1 property 1 required
GenericError
object
1 property 1 required
BrokerBusinessUserInvite
object
8 properties 1 required
AcceptBrokerInvite
object
8 properties 2 required
AgencySubscription
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

1fort-broker-api-openapi.yml Raw ↑

Other APIs 1Fort publishes across the network.

1Fort agent_runtime (v2) API
AE Profile APIs.io
1Fort Analytics API
AE Profile APIs.io
1Fort application: applications API
AE Profile APIs.io
1Fort application: clients API
AE Profile APIs.io
1Fort application (v2): applications API
AE Profile APIs.io
1Fort application (v2): coverages API
AE Profile APIs.io
1Fort Ascend API
AE Profile APIs.io
1Fort ascend (v2) API
AE Profile APIs.io
1Fort Auth API
AE Profile APIs.io
1Fort Authentication API
AE Profile APIs.io
1Fort billing (v2) API
AE Profile APIs.io
1Fort broker: ai-customization-types API
AE Profile APIs.io
#Brokers
← Back to 1 APIs
API Details
ID
1fort:1fort-broker-api
Base URL
https://api.1fort.com/apis/
Docs
https://api.1fort.com/api-docs
Provider
1Fort
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=1fort-broker-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/1fort-broker-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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 1Fort Broker 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.