Skip to main content
This guide details the primary data objects used in FrankieOne API requests and responses. Understanding these structures is essential for sending data correctly and interpreting the verification results.
An Address object contains the location details for an entity. Providing a complete, structured address is critical for successful verification against data sources.
Best Practices for Address DataFor optimal verification results, always provide addresses using structured fields rather than the longForm string. Supplying each component—such as streetNumber, streetName, locality, and country—enables more accurate matching and validation.
  • Break down addresses: Always separate address components into their individual fields wherever possible. While streetName can combine streetNumber, streetName, and streetType if needed, providing each field separately yields the most accurate results.
  • Address types:
    • RESIDENTIAL: The primary address used to determine the entity’s country of residence and current living address.
    • POSTAL: A mailing address. If a RESIDENTIAL address is not provided, this will be used as the default residential address.
  • Address status: Use the status field to indicate if the address is current or future. This helps in understanding the context of the address.
  • Updating addresses: Always include the addressId (returned when the address was first added) to ensure the correct record is modified.
  • Country codes: Ensure the country field is a valid ISO-3166-1 alpha-3 code (reference).
  • Building details: Include any building details, such as building level, in the buildingName field.

Common Address Fields

Maximum Lengths for NZ Addresses
For New Zealand addresses, the following maximum lengths are recommended:
  • Address line 1 (building name + unit number + street name + street type): 256 characters
  • Address line 2 (distinct to Frankie): 256 characters
  • Suburb: 50 characters
  • City: 50 characters
  • Postcode: 15 characters
A Document object represents a piece of identification provided by the user, such as a passport, driver’s license, or utility bill.
Document Class Guidance
When creating a document object, set the class field to IDENTITY for documents used to verify a person’s identity (such as passports or driver’s licenses). This ensures the document is processed correctly for identity verification checks.

Common Document Fields

An Issue is created by a workflow whenever a potential problem is detected that may require manual review. Your system should be designed to handle these issues, often by flagging the case for a compliance officer.

Key Issue Fields

The Risk Assessment object is returned as part of a workflowResult and contains the calculated risk profile for the entity based on your configured policies.

Key Risk Fields

Interpreting the status of a verification is critical. The API provides results at both the overall workflow level and for each individual step.

Common Workflow Statuses (workflowResult.status)

This tells you the final outcome of the entire verification process.

Common Step Results (workflowStepResults[].result)

This tells you the outcome of a specific check within the workflow.