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

Incognia Transactions API

Login and payment risk assessment

Incognia Transactions API is one of 4 APIs that Incognia publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

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

Requests are made against a single base URL, https://api.incognia.com/api.

1 operations 1 paths 13 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2
Base URL
https://api.incognia.com/api
Authentication
HTTP Basic, HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 3

Incognia Transactions API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (JWT) (bearerAuth). It supports OAuth 2.0 (oauth2) using the clientCredentials flow. By default, every request must be authenticated.

  • basicAuth — clientid and clientsecret sent as HTTP Basic credentials to the token endpoint.
  • bearerAuth — OAuth 2.0 bearer access token obtained from POST /v2/token.
  • oauth2 — OAuth 2.0 client-credentials grant. No scopes are defined; access is scoped by the credential's tenant.

Paths & Operations 1

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

Transactions 1

Login and payment risk assessment

POST
/v2/authentication/transactions
Register a login or payment transaction for risk assessment
registerTransaction body → 200400401403

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are TransactionRequest (20 properties), StructuredAddress (12 properties), TransactionAssessment (7 properties), PaymentMethod (5 properties). Each schema is shown below with its type and property counts.

TransactionAddress
object
4 properties
PaymentMethod
object
5 properties
StructuredAddress
object
12 properties
PersonID
object
2 properties
CardInfo
object
4 properties
TransactionRequest
object
20 properties 2 required
Error
object
Incognia error envelope.
1 property
Location
object
3 properties
RiskAssessment
string
Overall risk verdict returned by Incognia.
Coordinates
object
2 properties
TransactionAssessment
object
7 properties
PaymentValue
object
2 properties
Reason
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

incognia-transactions-api-openapi.yml Raw ↑

Other APIs Incognia publishes across the network.

Incognia Authentication API
Incognia Feedback API
Incognia Onboarding API
Where this information came from

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