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

Affinity auth API

Operations about auths

Affinity auth API is one of 11 APIs that Affinity 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 and API documentation.

This API exposes 1 operation across 1 path, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.affinity.co.

1 operations 1 paths 20 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.affinity.co
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Affinity auth API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

auth 1

Operations about auths

GET
/v2/auth/whoami
Get current user
v2_auth_whoami__GET → 200404default

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are User (4 properties), ValidationError (3 properties), WhoAmI (3 properties), Tenant (3 properties). Each schema is shown below with its type and property counts.

ServerError
object
2 properties 2 required
WhoAmI
object
WhoAmI model
3 properties 3 required
AuthorizationError
object
2 properties 2 required
MethodNotAllowedError
object
2 properties 2 required
UnsupportedMediaTypeError
object
2 properties 2 required
NotAcceptableError
object
2 properties 2 required
NotFoundError
object
2 properties 2 required
NotImplementedError
object
2 properties 2 required
Grant
object
3 properties 3 required
User
object
4 properties 4 required
UnprocessableEntityError
object
2 properties 2 required
Tenant
object
3 properties 3 required
Errors
object
1 property 1 required
ConflictError
object
2 properties 2 required
ValidationError
object
3 properties 3 required
Error
RateLimitError
object
2 properties 2 required
AuthenticationError
object
2 properties 2 required
NotFoundErrors
object
NotFoundErrors model
1 property 1 required
BadRequestError
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

affinity-auth-api-openapi.yml Raw ↑

Other APIs Affinity publishes across the network.

Affinity API V1
Affinity companies API
Affinity companyMerges API
Affinity emails API
Affinity lists API
Affinity meetings API
Affinity notes API
Affinity opportunities API
Affinity personMerges API
Affinity persons API
Where this information came from

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