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

1Fort Email AI Agent - Profiles API

**Access:** requires a JWT access token.

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

Tagged areas include Email AI Agent - Profiles. 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 11 operations across 7 paths, and defines 19 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/.

11 operations 7 paths 19 schemas 3 GET6 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
Resource Areas
1

Authentication & Security 2

1Fort Email AI Agent - Profiles 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 11

Across 7 paths, the API surfaces 11 operations — 3 GET, 6 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Email AI Agent - Profiles 11

Access: requires a JWT access token.

GET
/v2/broker/agent/profiles
Get Profile
agent_get_profile 1 param → 200401403404500
POST
/v2/broker/agent/profiles
Create Profile
agent_create_profile_v2 1 param body → 201400401403404500
PUT
/v2/broker/agent/profiles
Update Profile (Full Replace)
agent_update_profile_v2 1 param body → 200400401404403500
POST
/v2/broker/agent/profiles/search
Search Profiles (OpenSearch)
agent_search_profiles 1 param body → 200400401403404500
GET
/v2/broker/agent/profiles/{id}
Get Profile
agent_get_profile 2 params → 200401403404500
POST
/v2/broker/agent/profiles/{id}
Create Profile
agent_create_profile_v2 2 params body → 201400401403404500
PUT
/v2/broker/agent/profiles/{id}
Update Profile (Full Replace)
agent_update_profile_v2 2 params body → 200400401404403500
GET
/v2/broker/agent/profiles/{id}/business-candidates
Get Business Candidates
agent_get_business_candidates 2 params → 200401403404500
POST
/v2/broker/agent/profiles/{id}/create-business
Create Business from Profile
agent_create_business_from_profile 2 params body → 201400401403404409500
POST
/v2/broker/agent/profiles/{id}/link-business
Link Profile to Business
agent_link_profile_to_business 2 params body → 200400401403404409500
POST
/v2/broker/agent/profiles/{id}/link-email
Link Profile to Email
agent_link_profile_to_email 2 params body → 200400401403404500

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are AgentProfileUpsert (14 properties), AgentProfileDetail (12 properties), AgentBusinessCandidate (7 properties), AgentAddress (7 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
3 properties 1 required
AgentAddress
object
7 properties
AgentProfileLinkEmail
object
2 properties
AgentProfileLinkedEmail
object
3 properties
AgentBusinessCandidatesResponse
object
4 properties
AgentProfileLinkBusiness
object
1 property 1 required
AgentProfileUpsert
object
14 properties 1 required
AgentProfileUpsertResponse
object
4 properties
AgentPerson
object
4 properties 1 required
AgentProfileLinkEmailResponse
object
4 properties
AgentProfileLinkedAttachment
object
3 properties
AgentSourceDocument
object
3 properties 2 required
AgentProfileBusiness
object
3 properties
APIException
object
1 property 1 required
AgentBusinessCandidate
object
7 properties
AgentProfileCreateBusinessResponse
object
6 properties
AgentProfileLinkBusinessResponse
object
4 properties
AgentProfileDetail
object
12 properties
AgentProfileCreateBusiness
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

1fort-email-ai-agent-profiles-api-openapi.yml Raw ↑

Other APIs 1Fort publishes across the network.

1Fort agent_runtime (v2) API
1Fort Analytics API
1Fort application: applications API
1Fort application: clients API
1Fort application (v2): applications API
1Fort application (v2): coverages API
1Fort Ascend API
1Fort ascend (v2) API
1Fort Auth API
1Fort Authentication API
1Fort billing (v2) API
1Fort broker: ai-customization-types API
Where this information came from

This is an independent, third-party profile of 1Fort Email AI Agent - Profiles 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.