Trulioo · Arazzo Workflow

Trulioo Capture Detailed Consents And Verify

Version 1.0.0

Pull the full consent text to present to the end user, then verify with those consents recorded.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub Identity VerificationKYCKYBAMLWatchlist ScreeningBiometricsDocument VerificationFraud PreventionComplianceGlobal IdentityArazzoWorkflows

Provider

trulioo

Workflows

detailed-consents-and-verify
Retrieve detailed consent text, then verify with consents recorded.
Reads the detailed consent objects for a configuration/country pair so the integrator can present the text to the user, then runs a Verify carrying the list of consented datasource names.
2 steps inputs: configurationName, consentedDataSources, countryCode, dataFields outputs: detailedConsents, recordStatus, transactionRecordId
1
getDetailedConsents
Retrieve detailed consent metadata, including the text and summary to present to the end user for this configuration/country.
2
verify
Submit the Verify request recording the datasources the end user consented to after being shown the detailed consent text.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Trulioo Capture Detailed Consents And Verify
  summary: Pull the full consent text to present to the end user, then verify with those consents recorded.
  description: >-
    Regulated identity verification often requires presenting specific consent
    language to the end user before querying a datasource. This workflow fetches
    the detailed consent metadata (name plus the legal text and summary) for a
    country, then submits a Verify that records the named consents the user
    agreed to. Every step spells out its request inline so the flow can be read
    and executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: configurationApi
  url: ../openapi/trulioo-configuration-api-openapi.yml
  type: openapi
- name: verificationsApi
  url: ../openapi/trulioo-verifications-api-openapi.yml
  type: openapi
workflows:
- workflowId: detailed-consents-and-verify
  summary: Retrieve detailed consent text, then verify with consents recorded.
  description: >-
    Reads the detailed consent objects for a configuration/country pair so the
    integrator can present the text to the user, then runs a Verify carrying the
    list of consented datasource names.
  inputs:
    type: object
    required:
    - configurationName
    - countryCode
    - consentedDataSources
    - dataFields
    properties:
      configurationName:
        type: string
        description: Configured product/package name.
      countryCode:
        type: string
        description: Two-letter ISO 3166 country code.
      consentedDataSources:
        type: array
        items:
          type: string
        description: Names of datasources the end user has explicitly consented to.
      dataFields:
        type: object
        description: DataFields block for the verification.
  steps:
  - stepId: getDetailedConsents
    description: >-
      Retrieve detailed consent metadata, including the text and summary to
      present to the end user for this configuration/country.
    operationId: getDetailedConsents
    parameters:
    - name: configurationName
      in: path
      value: $inputs.configurationName
    - name: countryCode
      in: path
      value: $inputs.countryCode
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      detailedConsents: $response.body
  - stepId: verify
    description: >-
      Submit the Verify request recording the datasources the end user consented
      to after being shown the detailed consent text.
    operationId: verifyPerson
    requestBody:
      contentType: application/json
      payload:
        AcceptTruliooTermsAndConditions: true
        ConfigurationName: $inputs.configurationName
        CountryCode: $inputs.countryCode
        ConsentForDataSources: $inputs.consentedDataSources
        DataFields: $inputs.dataFields
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      transactionRecordId: $response.body#/Record/TransactionRecordID
      recordStatus: $response.body#/Record/RecordStatus
  outputs:
    detailedConsents: $steps.getDetailedConsents.outputs.detailedConsents
    transactionRecordId: $steps.verify.outputs.transactionRecordId
    recordStatus: $steps.verify.outputs.recordStatus

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/trulioo-detailed-consents-and-verify-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.