> ## Documentation Index > Fetch the complete documentation index at: https://docs.synctera.com/llms.txt > Use this file to discover all available pages before exploring further. # List verification results > List verification results. This endpoint will be removed in API v1. Use `GET /v0/verifications?customer_id={customer_id}` instead. ## OpenAPI ````yaml openapi.json get /customers/{customer_id}/verifications openapi: 3.0.3 info: description: >- This is the official reference documentation for Synctera APIs. If you need something specific or have a question, contact us.

license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html title: Synctera API version: 0.208.0 servers: - description: Sandbox (no real world financial impact) url: https://api-sandbox.synctera.com/v0 - description: Production url: https://api.synctera.com/v0 security: - bearerAuth: [] tags: - description: Lookup merchant information name: Merchants - description: Requests to generate simulated webhooks name: Card Webhook Simulations - description: >- Account programs define configurations for payment rails and transaction capabilities across different account types. name: Account Programs - description: Simulate receiving ACH transactions and returns name: ACH Transaction Simulations - description: Requests for risk evaluation and decisioning name: Risk Evaluations - description: Requests to link and manage External Cards name: External Cards - description: | The disclosures resource is used to track the status of disclosures and ensure that all parties have been shown the necessary disclosures to meet regulatory obligations. name: Disclosures - description: Create and manage Cash Order and Cash Deposit transfers name: Cash Orders and Deposits (alpha) - description: Requests to initiate customer verification. name: KYC Verification (deprecated) - description: Request to create and manage users name: Users - description: See balance history name: BalanceHistory - description: >- Migration mappings associate resources from an old tenant identity with a new tenant identity. name: Migration Mappings - description: | The External Account resource is used for managing links to accounts that operate outside of the Synctera ecosystem. name: External Accounts - description: Requests to create and manage account products, including fees, interest. name: Account Products - description: Requests to create and manage webhooks name: Webhooks - description: Create and manage documents. name: Documents - description: >- Create and manage same currency and multi-currency international wire transfers name: International Wires (alpha) - description: Requests for transaction risk detection name: Transaction risk - description: >- Used to configure bank accounts for which synctera accounts are considered a "subledger" to name: Bank Account - description: Request to create and manage party groups and party group members name: Party Groups - description: Requests to manage addresses name: Addresses - description: Requests to manage monitoring subscriptions and alerts for customers. name: Monitoring - description: Requests to search and manage compliance searches name: Compliance Searches - description: Requests to create and manage customers name: Customers - description: | The internal account resource is used for managing links to internal accounts where the funds are managed by integrators. name: Internal Accounts - description: Create and manage spending controls name: Spend Controls - description: Retrieve user identity information name: Identity - description: Requests to manage banks name: Banks - description: | The Disclosures resource is used to track the status of disclosures and ensure that customers have been shown the necessary disclosures to meet regulatory obligations. name: Disclosures (deprecated) - description: Create and manage wire transfers name: Wires - description: Requests to issue and manage Cards name: Cards - description: Request to create and manage edd name: Trust - description: Request to enroll, renew, or cancel watchlist monitors name: Watchlist (deprecated) - description: Endpoints for modifying or fetching posting dates name: Posting Dates - description: Transaction lines API name: transactions - description: Request to create and manage accounts name: Accounts - description: Requests to create and manage notes name: Notes - description: Account Template name: Account Templates - description: API for effective balances name: effective_balances - description: Requests to create and manage personal ID configurations name: Personal ID Configuration - description: > A natural person (individual human) that is relevant to the Synctera platform in some way: e.g. a personal customer or a director/officer/owner of a business. name: Persons - description: > Represents the relationships between parties. A relationship can exist between personal customers, business customers, or non-customer persons/organizations. name: Relationships - description: > A legal entity (corporation, partnership, etc.) that is relevant to the Synctera platform in some way: a business customer or some other organization that has an ownership share in such a business customer. name: Businesses - description: Request to create and manage payment_schedules name: Cronut - description: Requests to manage partners name: Partners - description: Request to create and manage deposits using remote deposit capture name: Remote Check Deposit - description: Requests to create and manage API keys name: API Keys - description: Requests to create and manage ban rules name: Ban Rules - description: Admin API for Middesk configuration using the tenants API keys. name: Middesk - description: Request to create and manage exclusions name: Stately - description: Request to create and manage partner configurations name: Quickstart - description: Manage contacts for bank and fintech partners name: Contacts - description: Create and manage transactions name: Transactions - description: Request to create and manage rdc configurations name: RDC Config - description: Create and manage holds name: Hold - description: Requests to create and manage roles name: Roles - description: Simulate receiving Wire transactions and returns name: Wire Transaction Simulations - description: Requests to create licenses name: Licenses - description: Requests to Admins to grant permissions to user name: Request Permissions - description: Configure vendor secrets for egress requests name: Egress Gateway Vendor Secret CRUD API - description: Requests to screen parties against sanctions watchlists name: Sanctions Screening - description: Create and manage payments name: ACH - description: Requests to calculate and manage CRR name: CRR - description: Requests to search financial institutions name: Institutions (Beta) - description: Create and manage tenant configurations name: Tenant Configs - description: Create and manage sweep configurations name: Configs - description: > Represents the compliance rules that are used to verify certain kinds of money movement. name: Compliance Rules - description: Configure webhook secrets for egress requests name: Egress Gateway Webhook Secret CRUD API - description: Create and manage transactions name: Transactions (internal) - description: History name: History - description: Create and manage EFT Canada transfers name: EFT Canada (Beta) - description: Requests to generate simulated transactions name: Card Transaction Simulations - description: Requests to initiate customer verification. name: KYC/KYB Verifications paths: /customers/{customer_id}/verifications: get: tags: - KYC Verification (deprecated) summary: List verification results description: > List verification results. This endpoint will be removed in API v1. Use `GET /v0/verifications?customer_id={customer_id}` instead. operationId: listVerifications parameters: - $ref: '#/components/parameters/customer_id_path' - $ref: '#/components/parameters/page_token' - $ref: '#/components/parameters/limit' - $ref: '#/components/parameters/include_history2' responses: '200': content: application/json: schema: $ref: '#/components/schemas/customer_verification_result_list' description: List of customer verification results. '400': $ref: '#/components/responses/bad_request' '401': $ref: '#/components/responses/unauthorized' '403': $ref: '#/components/responses/forbidden' '404': $ref: '#/components/responses/not_found' '500': $ref: '#/components/responses/internal_server_error' deprecated: true components: parameters: customer_id_path: description: The customer's unique identifier in: path name: customer_id required: true schema: $ref: '#/components/schemas/customer_id' page_token: in: query name: page_token schema: description: >- Optional pagination token to be provided to retrieve subsequent pages, returned from previous get example: a8937a0d type: string limit: in: query name: limit schema: default: 100 description: > Maximum number of objects to return per page. If the limit is greater than 100, then it will be set to 100. example: 100 minimum: 1 type: integer include_history2: description: If true, include old (inactive) records as well. in: query name: include_history schema: default: false type: boolean schemas: customer_verification_result_list: allOf: - properties: verifications: description: Array of verification results. items: $ref: '#/components/schemas/customer_verification_result' type: array required: - verifications type: object - $ref: '#/components/schemas/paginated_response' customer_id: example: 7d943c51-e4ff-4e57-9558-08cab6b963c7 format: uuid type: string customer_verification_result: description: Verification result properties: id: description: Unique ID for this verification result. example: 7d943c51-e4ff-4e57-9558-08cab6b963c7 format: uuid readOnly: true type: string issues: deprecated: true description: | List of potential problems found. These are subject to change. items: example: >- R186: Global Watchlist sources selected are correlated with the input identifiers type: string readOnly: true type: array raw_response: $ref: '#/components/schemas/raw_response' result: description: The determination of this verification. enum: - ACCEPTED - PROVIDER_FAILURE - PROVISIONAL - REJECTED - REVIEW example: ACCEPTED type: string vendor_info: $ref: '#/components/schemas/verification_vendor_info' verification_time: description: The date and time the verification was completed. format: date-time type: string verification_type: $ref: '#/components/schemas/kyc_verification_type' required: - result - verification_time - verification_type title: CustomerVerificationResult type: object paginated_response: properties: next_page_token: description: >- If returned, use the next_page_token to query for the next page of results. Not returned if there are no more rows. example: a8937a0d type: string title: Paginated List response type: object error: description: >- Synctera error responses in API v0 follow [RFC 7807](https://datatracker.ietf.org/doc/html/rfc7807). Following that standard, the field for a machine-readable "error code" in API v0 is `type`. In our future API v1, we are phasing out RFC 7807 and adopting a custom error format. That format will be documented in our API v1 spec. But you may see some v0 error responses with a machine-readable `code` field while we are making the transition from v0 to v1. properties: code: description: >- An optional “sneak preview” of our future API v1 error responses. This is provided to give integrators a chance to work with our future error codes. Error codes for the same error may change between v0 and v1. example: BAD_REQUEST_BODY type: string detail: description: | A human-readable string explaining this particular error. example: 'missing required fields: first_name, dob' type: string status: description: the HTTP status code for this response example: 400 type: integer title: description: > A human-readable string for this general category of error, which corresponds 1-to-1 with error types (`title` is the human-readable version of `type`). There can be multiple distinct titles for the same HTTP status code, and the same `title` can result in many different `detail` strings. This field will be removed in API v1. example: Bad Request Body type: string type: description: > A machine-readable string that identifies the error for programmatic use. This is a URI, i.e. a globally unique identifier. It is _not_ necessarily a URL, so do not expect it to resolve to a web page. You can use this whole string as an error code, or just everything after the last slash. This field will be removed in API v1. example: https://dev.synctera.com/errors/bad-request-body type: string title: Standard error response (RFC 7807 problem report) type: object raw_response: deprecated: true properties: provider: $ref: '#/components/schemas/provider_type' raw_data: description: Raw data from an external provider, as a JSON string. example: '{}' type: string title: Raw response from providers. type: object verification_vendor_info: description: > The information provided to Synctera from the vendor. Interpretation of this object is up to the client. discriminator: mapping: application/json: $ref: '#/components/schemas/verification_vendor_json' text/xml: $ref: '#/components/schemas/verification_vendor_xml' propertyName: content_type oneOf: - $ref: '#/components/schemas/verification_vendor_xml' - $ref: '#/components/schemas/verification_vendor_json' type: object kyc_verification_type: description: The type of check run on the customer. enum: - addressrisk - alertlist - decision - documentverification - emailrisk - fraud - kyc - phonerisk - social - synthetic - watchlistplus - watchlistpremier - watchliststandard example: kyc type: string provider_type: description: Name of the organization that provided this data. enum: - IDOLOGY - SOCURE example: SOCURE type: string verification_vendor_json: properties: content_type: description: Describes the content-type encoding received from the vendor. enum: - application/json type: string details: description: Array of vendor specific information. items: $ref: '#/components/schemas/verification_vendor_info_detail' readOnly: true type: array json: description: Data representation in JSON. type: object vendor: description: Name of the vendor used. example: SOCURE type: string required: - content_type - json - vendor verification_vendor_xml: properties: content_type: description: Describes the content-type encoding received from the vendor. enum: - text/xml type: string details: description: Array of vendor specific information. items: $ref: '#/components/schemas/verification_vendor_info_detail' readOnly: true type: array vendor: description: Name of the vendor used. example: IDOLOGY type: string xml: description: Data representaion in XML. type: string required: - content_type - vendor - xml verification_vendor_info_detail: properties: code: description: Vendor specific code. example: R186 type: string description: description: Description of vendor specific code. example: >- Global Watchlist sources selected are correlated with the input identifiers type: string type: object responses: bad_request: content: application/problem+json: schema: $ref: '#/components/schemas/error' description: BadRequest unauthorized: content: application/problem+json: schema: $ref: '#/components/schemas/error' description: Unauthorized forbidden: content: application/problem+json: schema: $ref: '#/components/schemas/error' description: Forbidden error not_found: content: application/problem+json: schema: $ref: '#/components/schemas/error' description: Resource not found internal_server_error: content: application/problem+json: schema: $ref: '#/components/schemas/error' description: Internal server error securitySchemes: bearerAuth: bearerFormat: api_key scheme: bearer type: http ````