NOTE: Australian companies ONLY.
Create or find and update an ORGANISATION type entity, then run the requested reports. Reports include:
At a minimum, you just need to supply an ACN and/or ABN and an entity type set to ORGANISATION. Alternatively the entity ID of an existing ORGANISATION entity gan be given in the request body
Note: these reports are different to the Ultimate Beneficial Owner and Business Detail requests - these reports are independent data and analysis over and above company information and verification details.
You can request multiple reports to be run at once and they will be returned as a group.
If a PDF report is requested then that report will be generated over time, so a temporary response with only the JSON reports will be returned and a webhook notification will be pushed later once the PDF report has been completed.
Customer ID issued by Frankie Financial. This will never change. Your API key, which is mapped to this identity, will change over time.
If, as a Frankie Customer, you are acting on behalf of your own customers, then you can populate this field with a Frankie-assigned ID.
Note: If using a CustomerChildID, you will also need a separate api_key for each child.
Any documents, checks, entities that are created when this field has been populated will now be tied to this CustomerID + CustomerChildID combination. Just as Customers cannot see data created by other Customers, so too a Customer’s Children will not be able to see each other’s data.
A Customer can see the documents/entities and checks of all their Children.
Open string that can be used to define the “channel” the request comes in from. It can potentially be used in routing and risk calculations upon request. Default values that can be used are:
Any alphanumeric string is supported though. Anything over 64 characters will be truncated.
Define the report(s) you wish to run.
You can request more than one as a comma separated list. Duplicates will be ignored.
Note: These reports are different to the business details and UBO queries and are meant to provide deeper detail and background on a business or organisation.
Current valid report types are:
Should the report(s) also be generated as a PDF document.
Collection of address objects.
When an entity is first created, it is assigned an ID. When updating an entity, make sure you set the entityId One exception to this is when an entity is created from a document object. It is expected that this object would be passed into a /check or /entity call to set it.
If the entity is using the new profiles feature, then their profile name will be found here.
Note: If setting a profile, you must ensure that the profile matches a known configuration.
See here for valid values: https://apidocs.frankiefinancial.com/docs/test-entity-verification
Indicates the type of an entity.
Set of key-value pairs that provide arbitrary additional type-specific data. You can use these fields to store external IDs, or other non-identity related items if you need to. If updating an existing entity, then existing values with the same name will be overwritten. New values will be added.
See here for more information about possible values you can use: https://apidocs.frankiefinancial.com/docs/key-value-pairs
Used to set additional information flags with regards to this entity and for ongoing processing.
Flags might include having the entity (not) participate in regular pep/sanctions screening Others will follow over time.
Used to indicate of the entity in question is:
Collection of identity documents (photos, scans, selfies, etc)
Organisation details for entities. Returned from an ASIC report.
The request was valid and was successfully processed. The report was run and the results have been attached.
Unique Frankie identifier for the report operation.
Describes all of the data being used to verify an entity.
Unique identifier provided by the service.
The collection of requested business reports.
Unique identifier for every request. Can be used for tracking down answers with technical support.
Uses the ULID format (a time-based, sortable UUID)
Note: this will be different for every request.