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 Auth API

Sign in / sign up via Google or Office365 OAuth and refresh JWT access tokens.**Access:** mixed; some endpoints are public, others require JWT (per endpoint).

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

Tagged areas include Authentication. 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 8 operations across 6 paths, and defines 4 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/.

8 operations 6 paths 4 schemas 2 GET6 POST

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 Auth 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 8

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

auth 8

Sign in / sign up via Google or Office365 OAuth and refresh JWT access tokens. Access: mixed; some endpoints are public, others require JWT (per endpoint).

POST
/auth/google/signin
Sign in with Google
auth_google_signin_create body → 200400403404500
POST
/auth/google/signup
Sign up with Google
auth_google_signup_create body → 200400403404500
POST
/auth/logout
Create Logout
auth_logout_create → 201403404500
GET
/auth/office365/signin
Sign in with Office365 (authorization code)
auth_office365_signin_list 1 param → 200400500
POST
/auth/office365/signin
Sign in with Office365 (access token)
auth_office365_signin_create body → 200400403404500
GET
/auth/office365/signup
Sign up with Office365 (authorization code)
auth_office365_signup_list 1 param → 200400500
POST
/auth/office365/signup
Sign up with Office365 (access token)
auth_office365_signup_create body → 200400403404500
POST
/auth/token/refresh
Create Refresh
auth_token_refresh_create body → 201400403404500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are TokenRefresh (2 properties), GenericError (1 property), APIException (1 property), ValidationError (1 property). Each schema is shown below with its type and property counts.

TokenRefresh
object
2 properties 1 required
ValidationError
object
1 property
APIException
object
1 property 1 required
GenericError
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

1fort-auth-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 Authentication API
1Fort billing (v2) API
1Fort broker: ai-customization-types API
1Fort broker: ai-customizations API
Where this information came from

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