FincenFetch
API docs by Redocly

FincenFetch Fetch API (2.6.0)

Download OpenAPI specification:

E-mail: file@fincenfetch.com URL: https://www.fincenfetch.com

This is the most recent publicly available API for interacting with FincenFetch Firm report records. This API can be used to start new reports and get updates on existing reports. All API endpoints are secured via bearer tokens that can be generated in the FincenFetch API portal at https://app.fincenfetch.com.

Reports

Operations related to FincenFetch BOI Reports

Get existing report index

Get a list of existing reports

Authorizations:
BearerAuth
query Parameters
limit
number <= 250
Default: 100

Maximum number of records to return on query

offset
number
Default: 0

Number of records to skip on query

sort
string
Enum: "report_guid" "report_type" "created_at" "deadline" "status" "progress" "delayed_invitation" "marked_filed_date" "transcript_url"

Field to sort by

direction
string
Default: "ASC"
Enum: "ASC" "DESC"

Direction to sort the data on

Responses

Request samples 

curl "https://api.fincenfetch.com/v2/reports" \
     -H 'Accept: application/json' \
     -H 'Authorization: Bearer YOUR_API_TOKEN'

Response samples

Content type
application/json
{
  • "status": "200",
  • "detail": [
    ],
  • "info": {
    }
}

Create reports

Start new BOI reports

Duplicate Reports

When processing a report creation request, the FincenFetch API will check for existing un-filed reports with matching company information. If a report already exists for the provided company, the API will return the existing report details and will not create a new report.

Data Validation

When creating multiple reports, all data will be validated before report creation. In the event of data validation errors, no reports will be created and all errors will be returned in the response body. In short, the FincenFetch API will not create any reports in a request unless it is able to successfully create all requested reports.

Applicant Data

Reports can be pre-populated with applicant data only if the applicant has a valid FinCEN ID. To pre-populate an applicant, provide the fincen_id in the applicants array. If the applicant does not have a FinCEN ID, the applicant will need to be completed via the FincenFetch portal.

Beneficial Owner Data

Reports can be pre-populated with beneficial owner data by either including the owner's FinCEN ID or inviting them to complete their information by providing their email address.

Authorizations:
BearerAuth
Request Body schema: application/json
required
One of
required
Array of objects [ 1 .. 100 ] items

Responses

Request samples

Content type
application/json
Example
{
  • "company_name": "Company Name, LLC",
  • "company_email": "admin@example.com",
  • "office_guid": "G-375ed018-d0ff-76f5-4c4c-19917ee8ce97",
  • "company_type": "llc",
  • "ein": "212121212",
  • "formation_state": "OH",
  • "office_address1": "123 Main Street",
  • "office_address2": "Suite 201",
  • "office_city": "Columbus",
  • "office_state": "OH",
  • "office_zip": "43081",
  • "dbas": [
    ],
  • "applicants": [
    ],
  • "owners": [
    ],
  • "billing_account": "123456789",
  • "optional_params": [
    ]
}

Response samples

Content type
application/json
Example
{
  • "status": 200,
  • "detail": {
    }
}

Get an existing report

Get details of an existing report

Additional report details

When querying the /v2/reports/{report_guid} endpoint, additional information can be requested depending on your applications needs by using the with query parameter. The following options are available, and multiple may be passed in a single request:

  • pii - Include report-level personally identifiable information (PII) in the response
  • owners - Include beneficial owner PII in the response
  • applicants - Include applicant PII in the response
  • company - Include company details in the response
  • invited_owners - Include invited owner details in the response
Authorizations:
BearerAuth
path Parameters
report_guid
required
string <guid> (ReportGuid) ^R-[0-9a-f-]{8}-[0-9a-f-]{4}-[0-9a-f-]{4}-[0-...
Example: R-46646532-c06f-c001-4c4c-10bfbd84030b

Unique identifier for a report

query Parameters
with
Array of strings
Items Enum: "pii" "owners" "applicants" "company" "invited_owners"

Responses

Request samples 

REPORT_GUID='R-32186594-08bd-ff7c-4c4c-de91930de998'
curl "https://api.fincenfetch.com/v2/reports/$REPORT_GUID?with[]=owners&with[]=applicants" \
     -H 'Accept: application/json' \
     -H 'Authorization: Bearer YOUR_API_TOKEN'

Response samples

Content type
application/json
{
  • "status": "200",
  • "detail": {
    }
}

Offices

Operations related to firm offices

Get an existing office

Get details of an existing office

Authorizations:
BearerAuth
path Parameters
office_guid
required
string <guid> (OfficeGuid) ^G-[0-9a-f-]{8}-[0-9a-f-]{4}-[0-9a-f-]{4}-[0-...
Example: G-034eeee5-7e0e-59f5-4c4c-4e8f3ffbe016

Unique identifier for an office

Responses

Request samples 

OFFICE_GUID='G-32186594-08bd-ff7c-4c4c-de91930de998'
curl "https://api.fincenfetch.com/v2/offices/$OFFICE_GUID" \
     -H 'Accept: application/json' \
     -H 'Authorization: Bearer YOUR_API_TOKEN'

Response samples

Content type
application/json
{
  • "status": "200",
  • "detail": {
    }
}

Get existing office index

Get a list of existing offices

Authorizations:
BearerAuth
query Parameters
limit
number <= 250
Default: 100

Maximum number of records to return on query

offset
number
Default: 0

Number of records to skip on query

sort
string
Enum: "office_guid" "office_name" "internal_name" "created_at"

Field to sort by

direction
string
Default: "ASC"
Enum: "ASC" "DESC"

Direction to sort the data on

Responses

Request samples 

curl "https://api.fincenfetch.com/v2/offices" \
     -H 'Accept: application/json' \
     -H 'Authorization: Bearer YOUR_API_TOKEN'

Response samples

Content type
application/json
{
  • "status": "200",
  • "detail": [
    ],
  • "info": {
    }
}