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

SoFi Tech Solutions Risk API 2.0

Identity verification for consumers and businesses - verify a customer, read application and customer status, close an application, and retrieve verification documents and rule outcomes. This is the IVS surface that Create Account calls when the EIVS provider parameter is set, exposed directly for callers that want to verify before they open anything.

SoFi Tech Solutions Risk API 2.0 is one of 11 APIs that SoFi Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Fintech, Payments, Banking, Card Issuing, and Banking as a Service. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 6 operations across 6 paths, and defines 35 schemas. It is described by OpenAPI 3.1.0, at version 2.0.

Requests are made against a single base URL, {corename}.risk.{env}.gpsrv.com//.

6 operations 6 paths 35 schemas 6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0
Base URL
https://{corename}.risk.{env}.gpsrv.com/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

SoFi Tech Solutions Risk API 2.0 declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (gft-internal-service-auth).

Paths & Operations 6

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

IVS 6
POST
/ivs/2.0/verifyCustomer
Verify Customer
risk2_post_ivs-2-0-verifycustomer 2 params body → 200400401403404409429500
POST
/ivs/2.0/getApplicationStatus
Get Application Status
risk2_post_ivs-2-0-getapplicationstatus 2 params body → 200400401403404409429500
POST
/ivs/2.0/closeApplication
Close Application
risk2_post_ivs-2-0-closeapplication 2 params body → 200400401403404409429500
POST
/ivs/2.0/getCustomerStatus
Get Customer Status
risk2_post_ivs-2-0-getcustomerstatus 2 params body → 200400401403404409429500
POST
/ivs/2.0/closeCustomer
Close Customer Account
risk2_post_ivs-2-0-closecustomer 2 params body → 200400401403404409429500
POST
/ivs/2.0/getVerificationDocuments
Get Verification Documents
risk2_post_ivs-2-0-getverificationdocuments 2 params body → 200400401403404409429500

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are BusinessEntity (29 properties), PersonEntity (27 properties), LNRuleOutcome (12 properties), Application (9 properties). Each schema is shown below with its type and property counts.

BusinessEntity
object
29 properties 8 required
BusinessMailingAddress
object
6 properties 5 required
BusinessRegAddress
object
6 properties 5 required
PersonEntity
object
27 properties 8 required
PersonEntityRoles
string
ResidentialAddress
object
6 properties 5 required
VerifyCustomerType
string
GSAPIErrorDetail
object
Provides additional information about the error.
3 properties 2 required
Application
object
9 properties
CustomerVerificationResult
string
RuleOutcome
object
4 properties
RulesetOutcomes
object
3 properties
CloseReasonType
string
DocumentPage
object
2 properties 2 required
VerificationDocument
object
3 properties 3 required
LNDecisionReason
object
Decision reason model for LN Referral webhook.
2 properties
LNDocument
object
Document model for LN Document Submitted webhook.
3 properties
LNDocumentPage
object
Document page model for LN Document Submitted webhook.
1 property
LNFlag
object
Flag model for LN Referral webhook.
2 properties
LNNextAction
object
Next action model for LN Referral webhook.
2 properties
EmptyDict
object
LNDecision
object
1 property 1 required
LNDecisionCode
string
LNProgressStatusCode
string
LNStatus
object
2 properties 2 required
LNDocumentLink
object
Link model for document requested webhook links.
2 properties
LNCountry
object
2 properties 2 required
LNJourneyStatus
object
8 properties
LNJourneyType
object
2 properties
LNJourneyappOutomes
object
5 properties
LNLink
object
Link model for HATEOAS links.
2 properties
LNRuleOutcome
object
12 properties
LNRuleSetOutcome
object
6 properties
LrsIngestError
object
7 properties 3 required
LrsIngestErrorDetail
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sofi-technologies-risk-api-2-0-openapi.json Raw ↑

Other APIs SoFi Technologies publishes across the network.

SoFi Tech Solutions Program API
SoFi Tech Solutions Payment Hub API 2.0
SoFi Tech Solutions Dispute API 3.0
SoFi Tech Solutions Dispute API 2.0
SoFi Tech Solutions Loan API
SoFi Tech Solutions Risk API 1.0
SoFi Tech Solutions Public Config API
SoFi Tech Solutions Events API
SoFi Tech Solutions Auth API
SoFi Tech Solutions External Trans API
Where this information came from

This is an independent, third-party profile of SoFi Tech Solutions Risk API 2.0, 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.