FundsConfirmationResults
The FundsConfirmationResults resource allows for polling for results from the Funds Confirmation service.
| API | Description |
|---|---|
| GET web_api/funds_confirmation_results?resultsDate={resultsDate} |
Retrieve Funds Confirmation results for a specified date. If the resultsDate parameter is not included in the request, the default value is the current date. |
ActivityReports
The Activity Reports resource is used to run reports that show an API user's activity summary. The reports include a count of total inquiries, a count of inquiries broken down by each service type, and group by counts of results values for AccountResponseCode and CustomerResponseCode.
| API | Description |
|---|---|
| GET web_api/activity_reports_v5_8?start={start}&end={end} |
Get an Activity Report (Version 5.8) for a date range. If the start or end parameter is not included in the request, then the default value for start is midnight Central time zone for the current day, and the default value for end is the current date and time. |
| GET web_api/activity_reports_v5_9?start={start}&end={end} |
Get an Activity Report (Version 5.9) for a date range. If the start or end parameter is not included in the request, then the default value for start is midnight Central time zone for the current day, and the default value for end is the current date and time. |
IdMonitoring
The Id Monitoring resource allows the user to manage monitored entities and retrieve identity monitoring alerts.
| API | Description |
|---|---|
| GET web_api/id_monitor |
Retrieve the full Identity Monitor list for the authenticated API user. |
| GET web_api/id_monitor/{Start}/{End} |
Retrieve active Identity Monitor alerts for a specified date range. |
PrivateBadChecks
The Private Bad Checks resource allows management of your API user's Private Bad Checks list.
| API | Description |
|---|---|
| POST web_api/private_bad_checks |
Add a new Private Bad Check item to the authenticated user's list. |
| GET web_api/private_bad_checks |
Retrieve the complete Private Bad Checks list for the authenticated API user. |
| GET web_api/private_bad_checks/{id} |
Retrieve a single Private Bad Check item by its unique identifier. |
| PATCH web_api/private_bad_checks/{id} |
Toggle a current Private Bad Check item's status between Active and Inactive |
Status
The Status resource provides a health-check endpoint that returns the current build version and operational status of the Verification Services API.
| API | Description |
|---|---|
| GET web_api/status |
Retrieve the current health status and build information of the API. |
MobileConsent
The Mobile Consent resource allows management of Mobile Consent Records required to use the gMobile services. You can add new consent records, retrieve existing consent records, and revoke existing consent records.
| API | Description |
|---|---|
| GET web_api/mobile_consent/consent_text |
Retrieve the end-user agreement statement required for use of the gMobile service. Note: the returned text contains a [CompanyName] placeholder that must be replaced with your company name before displaying to the end user. |
| POST web_api/mobile_consent/{phoneNumber}/records |
Record a new mobile consent record for a phone number. |
| GET web_api/mobile_consent/{phoneNumber}/records |
Retrieve all mobile consent records for a specified phone number. |
| GET web_api/mobile_consent/{phoneNumber}/records/{id} |
Retrieve a single mobile consent record by its unique identifier. |
| PATCH web_api/mobile_consent/{phoneNumber} |
You must allow your customer to revoke gMoblie consent for their phone number. Once a consent record has been set to not valid, your API user cannot make gMobile enabled inquiries on the phone number until a new valid consent is recorded for the phone number. |
Inquiries
The Inquiries resource allows access to the gVerify, gAuthenticate, gIdentify, CustomerID, gOFAC, and gMobile services. Each inquiry can be configured to run one or more services based on your API user's permissions. For GIACT's SecureLink suite of services, see the SecureLink resource.
| API | Description |
|---|---|
| POST web_api/inquiries_v5_8 |
Submit a new inquiry to the Verification Services API (Version 5.8) for processing. |
| POST web_api/inquiries_v5_9 |
Submit a new inquiry to the Verification Services API (Version 5.9) for processing. |
| GET web_api/inquiries_v5_8/{id} |
Retrieve a previous inquiry result (Version 5.8) by its ItemReferenceId. |
| GET web_api/inquiries_v5_8/{start}/{end} |
Search all inquiries (Version 5.8) by date range and/or inquiry data submitted. |
| GET web_api/inquiries_v5_9/{id} |
Retrieve a previous inquiry result (Version 5.9) by its ItemReferenceId. |
| GET web_api/inquiries_v5_9/{start}/{end} |
Search all inquiries (Version 5.9) by date range and/or inquiry data submitted. |
JPMLink
The JPM Link resource provides integration with the JPM Liink platform for account verification inquiries. Authorized Liink clients can submit debtor or creditor verification requests for processing.
| API | Description |
|---|---|
| POST web_api/JPMLinkInquiryPost |
Submit a new JPM Liink inquiry request for debtor or creditor account verification processing. |
SecureLink
The SecureLink resource provides access to GIACT's SecureLink suite of services, including Confirmation Questions, Security Codes, and Mobile Locations.
| API | Description |
|---|---|
| POST web_api/securelink/confirmation_questions/sms |
Submit a new SecureLink Confirmation Question request via SMS text message. |
| POST web_api/securelink/confirmation_questions/ivr |
Submit a new SecureLink Confirmation Question request via IVR phone call. |
| GET web_api/securelink/confirmation_questions/{id} |
Retrieve the result of a SecureLink Confirmation Question request by its RequestId. |
| POST web_api/securelink/security_codes/sms |
Submit a new SecureLink Security Code request via SMS text message. An out-of-band secret code is sent to the end user; the code is not exposed to the API consumer. |
| POST web_api/securelink/security_codes/email |
Submit a new SecureLink Security Code request via Email. An out-of-band secret code is sent to the end user; the code is not exposed to the API consumer. |
| GET web_api/securelink/security_codes/{id}/verifications |
Check whether a verification attempt has been made for a Security Code request. |
| POST web_api/securelink/security_codes/{id}/verifications |
Verify that the Security Code value given to you by your end user matches the value that was sent to the phone number or email address in the Security Code request. |
| POST web_api/securelink/mobile_locations |
Submit a new SecureLink Mobile Location request to the end user's mobile device. |
| GET web_api/securelink/mobile_locations/{id} |
Retrieve the Mobile Location result for a previously submitted request. |
ErrorLogItems
The Error Log Items resource provides access to inquiries that returned error messages. Check the error log regularly to identify and resolve issues with your integrated application. Each error log item includes the inquiry object that was posted and the error message returned.
| API | Description |
|---|---|
| GET web_api/error_log_items?start={start}&end={end} |
Search the Error Log using a date range. If the start or end parameter is not included in the request, then the default value for start is midnight Central time zone for the current day, and the default value for end is the current date and time. |
| GET web_api/error_log_items/{id} |
Retrieve a single error log item by its unique identifier. |
Authenticate
The Authenticate resource provides token-based authentication for the Verification Services API. Clients exchange their credentials (client_id and client_secret) for a JWT access token.
| API | Description |
|---|---|
| POST web_api/authenticate |
Authenticate using client credentials and receive a JWT access token. |
GScanItems
The gScan Items resource allows access to the gScan OCR and barcode scanning services. You can submit images of checks and/or ID cards for optical character recognition and barcode processing.
| API | Description |
|---|---|
| POST web_api/gscanitems_v5_8 |
Submit a new gScan OCR request (Version 5.8) for processing. |
| GET web_api/gscanitems_v5_8/{id} |
Retrieve a previous gScan OCR result (Version 5.8) by its GScanItemId. |
| POST web_api/gscanitems_v5_9 |
Submit a new gScan OCR request (Version 5.9) for processing. |
| GET web_api/gscanitems_v5_9/{id} |
Retrieve a previous gScan OCR result (Version 5.9) by its GScanItemId. |
GIdentify
gIdentify "fast path" controller (POC). PURPOSE ======= A high-volume internal consumer (the sister company, "WV") sends gIdentify identity verification calls, the majority of which carry a full 9-digit SSN (TID). The normal v5.9 pipeline ( -> RunProducts) is a large orchestrator that runs many products and, for gIdentify, ultimately calls the heavyweight Equifax search stored procedure (usp_EFXAddressNameSearch, ~400-486ms). This controller is a deliberately lean path that, for TID-carrying calls, routes through the TID-first Vendor Services WebMethod so the database can use the fast usp_EFXLastLookup seek (~5-44ms). WHAT IT DELIBERATELY REUSES (no duplication, no behavior drift): • ApiUsers_GetSettings -> the same per-user settings read as the normal flow, so product flags (e.g. ReturnPersonTaxId, MasterDeathFileEnabled) come from the user's real entitlements rather than hard-coded constants. • AuthorizeApiUserForServicePermissions -> the same service-permission authorization; this endpoint cannot be privately gated, so the entitlement check must run here too. • ModelState / null / PreProcessInquiry / ValidateInquiry -> identical request validation and input normalization as the normal v5.9 flow. • EquifaxPerson.CallForGIdentifyFastPath -> the same matching, FilterResults scoring, alert generation, response-code determination, SSN masking and audit save as the normal flow. • VersionConversionHelper -> identical v5.8 -> v5.9 result mapping. • Repository.ReferenceItems_Add (v5.9) -> identical billing / reference-item write. WHAT IT DELIBERATELY SKIPS (lean path + POC scope): • The full RunProducts orchestration -> only the gIdentify person product runs. The service is hard-coded to identifyperson (caller-supplied ServiceFlags are not parsed), and there is no TransUnion/EVS fallback cascade (Equifax-only). • KBA, Identity Monitoring, Identity Scoring and all global/international (GDC) handling are off for this POC. • gOFAC and CMRA post-processing -> pending a WV decisioning answer (see leadership note). Neither changes the identity match code; both can affect the aggregate verdict and the alert list, so they are tracked as a go-live decision, not a build blocker. AUTH ==== Reuses the existing Basic Auth + IP-whitelist gate (same mechanism as web_api/inquiries_v5_9), so WV authenticates with the credentials they already hold — no new key to manage for the POC. (A future, more comprehensive version may move to an X-Api-Key / private-endpoint model.) SCOPE ===== All traffic for this endpoint is domestic (US) and person-only gIdentify. Those assumptions are encoded as the InternationalInquiry constant below and the hard-coded gIdentify-person service flag, and are intentional for the POC.
| API | Description |
|---|---|
| POST web_api/gidentify |
Submit a gIdentify identity-verification inquiry through the lean TID-first fast path. |