1. Introduction
DataDock provides developers with real-time access to:
Our APIs are designed to be secure, scalable, and high-performance, enabling businesses to integrate critical compliance and property-related data into their applications seamlessly.
1.1 Base URLs
Dashboard URL
The dashboard is available at:
https://app.datadock.ai
API Base URL
All API requests must be sent to:
https://api.datadock.ai
2. Getting Started
2.1 Registration
Recommended Method — Dashboard Registration
It is strongly recommended that users register through the dashboard:
https://app.datadock.ai
From the dashboard, users can:
1) Create an account easily
Upon successful registration, you will get an email.
Then click on the link to verify your account, once done it takes you to the log in page.
Alternative Method — Register via API Endpoint
Developers may also register directly through the API:
Endpoint:
POST /auth/register
{
"username": "your_username",
"email": "your_email@example.com",
"password": "your_secure_password"
}
Sample Response
{
"message": "User registered. Please check your email to verify your account and get your API token.”
}
2.2 Email Verification
After registration (either via dashboard or API), users receive an email containing:
- A verification link
- Their API token
Sample Email:
Subject: Welcome to Datadock!
Hello,
Welcome to Datadock!
Here is your API token:
c49ca84bcc452f873********b280776d
To verify your email address and activate your API token, click the link below: below:
https://api.datadock.ai/auth/verify?email=you@example.com
Thanks for joining us!
— The Datadock Team
Once the email is verified, the token becomes active and can be used immediately to access the APIs.
2.3 Authentication
All protected endpoints (e.g., /api/v1/filingflow, /api/v1/globalcomply) require the API token to be included in the request header.
Header Format
Authorization: Bearer your_api_token
Example Request
GET /api/v1/ filingflow?form_type=form_8k
Authorization: Bearer c49ca84bcc452f873********b280776d
If the token is missing or invalid, the API will return an authentication error.
2.4 Rate Limiting
To ensure reliable performance for all users, rate limits apply:
- Default: 100 requests per hour
- High-load endpoints: 5 requests per minute
3. FilingFlow Query API – US Security and Exchange Commission
The FilingFlow API enables querying metadata from U.S. Securities and Exchange Commission (SEC) filings across various form types.
The data is pulled from the EDGAR index and made available for structured search and export.
Each filing is returned in JSON format, containing metadata such as company name, form type, filing and event dates, geographic info, reporting persons, and filing sources.
3.1 Use Cases
- Monitor institutional investors (e.g., BlackRock 13F-HR filings).
- Screen for startup/private placement activity via Form D.
- Export filtered filings to JSON or Excel.
3.2 Global Filterable Fields
- Filter keys available globally:
- form_type: e.g., 13F-HR, D, 10k
- company_name
- cik
- accession
- filing_date
- city
- state
- zipcode,
- former_name
- event_date
- name_address
- names_of_reporting_persons
- owner_cik
- issuer_name
- owner_name
- report_period
- address
- report_type
- filer_cik
- issuer_cik
- issuer_city
- issuer_state
- issuer_zip
- owner_zip
- issuer_symbol
- cusip
Range Filters
- filing_date_min, filing_date_max
- report_period_min, report_period_max
Key Features:
- Form-specific tables by type (e.g., sec.13f_hr, sec.d).
- support partial (contains) and case-insensitive matches unless configured otherwise.
- Export results in .json, .json_download, or .excel.
- Offset-based pagination for smooth UI/UX integration
3.3 Example Queries
GET
https://api.datadock.ai/api/v1/filingflow?form_type=FORM
13FHR&filer_cik=0000123456
{
"count": 1,
"results": [
{
"schema_location": "example_value",
"schema_version": "example_value",
"document_type": "example_value",
"livetest_flag": "example_value",
"confirming_copy_flag": "example_value",
"return_copy_flag": "example_value",
"filing_website_notice_flag": "example_value",
"filer_cik": "0000123456"
}
]
}
3.4 Step-by-Step Guide
Step 1: Install and Set Up Postman
- Method: GET
- URL: https://datadock.ai/api/v1/filingflow
Parameters:
- form_type (required)
- company_name
- filing_date_min, filing_date_max
- format: json | json_download | excel
3.5 Query Parameters
| Parameter | Type | Description | Example Request |
|---|---|---|---|
| form_type | String | Required. The type of FilingFlow form (e.g. form_10k, form_8k, form_13f_hr, form_d, form_sc_13d, form_sc_13g, form_13f_nt). | /api/v1/filingflow?form_type=form_13f_hr |
| company_name | String | Filter results by company name (partial match supported). | /api/v1/filingflow?form_type=form_13f_hr &company_name=Apple |
| filing_date | String | Filter by exact filing date (YYYY-MM- DD). | /api/v1/filingflow?form_type=form_13f_hr &filing_date=2024-02-01 |
| filing_date_min | String | Filter results from this date (YYYY- MM-DD). | /api/v1/filingflow?form_type=form_13f_hr &filing_date_min=2024-01-01 |
| name_address | String | Filter results based on name address. Avialable for only form_sc_13g and form_sc_13d | /api/v1/filingflow?form_type=form_sc_13 g&name_address=Inc. 595 Madison Avenue |
| names_of_repo rting_persons | String | Filter results based on the name of the reporting person. Avialable for only form_sc_13g and form_sc_13d | /api/v1/filingflow?form_type=form_sc_13 d&names_of_reporting_persons=Q Power LLC |
| filing_date_max | String | Filter results up to this date (YYYY- MM-DD). | /api/v1/filingflow?form_type=form_13f_hr &filing_date_max=2024-02-01 |
| format | String | Optional. Specifies the output format: json (default), json_download, or excel. | /api/v1/filingflow?form_type=form_13f_hr &format=excel |
| cik | string | Filters result based on the comapany’s cik number | /api/v1/filingflow?form_type=form_13f_hr &cik=1703079 |
| accession | string | Filters result based on the comapany’s accession number | /api/v1/filingflow?form_type=form_13f_hr&accession= 0001493152-24-033795 |
Supported Query Parameter:
This section describes which form types are applicable for each form.
| Form Name | Description | Filters available |
|---|---|---|
| Form 1012B | This is a registration statement filed with the U.S. Securities and Exchange Commission (SEC) under Section 12(b) of the Securities Exchange Act of 1934. | address, company_name, filing_date, filing_date_min, filing_date_max |
| Form 13fhr | Filed quarterly by institutional investment managers to disclose equity holdings | filer_cik, report_period, report_type, report_period_min, report_period_max |
| Form 13fnt | Initially quarterly 13F notice filings (no holdings table) for certain conditions | filer_cik, report_period, report_type, report_period_min, report_period_max |
| Form 1A | Regulation A offering statement (Form 1A). | issuer_cik, issuer_city, issuer_name, issuer_state, issuer_zip |
| Form 1a pos | Form 1A (posteffective amendments / offering statements). | issuer_cik, issuer_city, issuer_name, issuer_state, issuer_zip |
| Form 1aw | Form 1A Withdrawal letters / notices. | company_name, filing_date, filing_date_min, filing_date_max |
| Form 3 | Initial statement of beneficial ownership for insiders/insiders transactions. | issuer_cik, issuer_name, issuer_symbol, owner_cik, owner_name, owner_zip, report_period, report_period_min, report_period_max |
| Form 4 | Statement of changes in beneficial ownership (insider trades). | issuer_cik, issuer_name, issuer_symbol, owner_cik, owner_name, owner_zip, report_period, report_period_min, report_period_max |
| Form 5 | Annual statement of changes in beneficial ownership (catchup). | issuer_cik, issuer_name, issuer_symbol, owner_cik, owner_name, owner_zip, report_period, report_period_min, report_period_max |
| Form 8k | Also known as a “current report” and it is the report that companies must file with the SEC to announce major events that shareholders should know about. | former_name, issuer_symbol, owner_cik, owner_name, owner_zip, report_period, report_period_min, report_period_max |
| Form D | Official notice of an offering of securities that is made without registration under the Securities Act in reliance on an exemption provided by Regulation D and Section 4(a)(5) under the Act. | issuer_cik, issuer_city, issuer_name, issuer_state, issuer_zip |
| Form IRANNOTICE | Internal/agency notice (IRAN notice) — administrative communication. | filing_date, filing_date_min, filing_date_max |
| Form SC13D | Schedule 13D for beneficial ownership reporting for activist investors. | cusip, filing_date, issuer_name, filing_date_min, filing_date_max |
| Form SC13G | Schedule filed to report acquisition of beneficial ownership of 5% or more of a class of equity securities by passive investors and certain institutions. | cusip, filing_date, issuer_name, filing_date_min, filing_date_max |
4. GlobalComply Query API – Sanctions and Compliance
The GlobalComply API allows real-time filtering and export of sanctioned individuals, entities, ships, programs, and places from multiple official sources including OFAC, UK, EU, DFAT (Australia), Canada, and SECO (Switzerland).
Returned results include sanctioned names, aliases, identifiers, nationalities, addresses, program IDs, and relevant listing metadata all unified in JSON format.
4.1 Use Cases
- AML/KYC background checks.
- Vendor and partner screening.
- Regulatory compliance automation.
4.2 Filterable Fields
Searchable by:
- Personal names (first/last/middle, aliases).
- Program type, listing date.
- Country, citizenship, address, place of birth.
- Vessel or ship metadata (IMO number, flag, tonnage).
- Entity/business info: registration numbers, parent companies
Key Features:
- Supports 9 distinct sanctions sources via the sanctions_agency parameter.
- Smart range filtering: listing_date_min, etc.
- All sources normalized to shared fields for unified access.
- Fast export in .json, .json_download, or .excel.
4.3 Example Queries
GET
/api/v1/globalcomply?sanctions_agency=eu_sanctions&Naal_lastname=Putin&Leba_publication_date_min=2023-01-01
Important Note:
- sanctions_agency is a compulsory paramenter.
- The sanctions_agency arguments are;
- dfat_sanctions
- canada_sanctions
- eu_sanctions
- ofac_non_sdn_sanctions
- ofac_sdn_sanctions
- seco_place_sanctions
- seco+program_sanctions
- seco_target_sanctions.
Query Parameters:
| Parameter | Type | Description | Example Request | Sanction Agency |
|---|---|---|---|---|
| country | string | Country associated with the individual or entity | ?country=Russia | canada_sanctions |
| last_name | string | Last name of sanctioned individual | ?last_name=Ivanov | canada_sanctions |
| given_name | String | Given name of sanctioned individual | ?given_name=Ivan | canada_sanctions |
| aliases | String | Alternate names of individuals/e ntities | ?aliases=Natalia Mikhailauna Buhuk | canada_sanctions |
| entity | String | Entity name | ?entity=ACME Corp | canada_sanctions |
| date_of_li sting | String | Official listing date | ?date_of_listing =2020-09-28 | canada_sanctions |
| schedule | String | Associated sanction schedule | ?schedule=1, Part 1 | canada_sanctions |
| date_of_listing_min | String | Start date for listing filter | ?date_of_listing _min=2020-01-01 | canada_sanctions |
| date_of_listing_max | string | End date for listing filter | ?date_of_listing _max=2023-12-31 | canada_sanctions |
| Reference | string | Unique identifier in DFAT listing | ?Reference=DFAT1 234 | dfat_sanctions |
| Name of Individual or Entity | string | Name of subject | ?Name of Individual or Entity=John Smith | dfat_sanctions |
| Type | string | Subject type: individual, entity, ship | ?Type=Individual | dfat_sanctions |
| Place of Birth | string | Subject’s place of birth | ?Place of Birth=Moscow | dfat_sanctions |
| Citizenship | string | Country of citizenship | ?Citizenship=Canada | dfat_sanctions |
| Address | string | Address string | ?Address=123 Main Street | dfat_sanctions |
| Listing Information | string | Additional listing notes | ?Listing Information=Coun cil Decision | dfat_sanctions |
| Committees | string | Related committees | ?Committees=UNSC | dfat_sanctions |
| Date_file | string | File publication date | ?Date_file=2024- 01-01 | eu_sanctions |
| Entity_log ical_id | string | Logical ID of sanctioned entity | ?Entity_logical_ id=E123456 | eu_sanctions |
| Programme | string | Sanctions program | ?Programme=Russi a Program | eu_sanctions |
| Naal_lastn ame | string | Last name in natural person data | ?Naal_lastname=P etrov | eu_sanctions |
| Naal_first name | string | First name in natural person data | ?Naal_firstname= Alexei | eu_sanctions |
| Addr_country | string | Country part of the address | ?Addr_country=Fr ance | eu_sanctions |
| Birt_place | string | Place of birth | ?Birt_place=Kiev | eu_sanctions |
| EU_ref_num | string | Official EU reference number | ?EU_ref_num=EU20 23/456 | eu_sanctions |
| last_update | string | Last update date for UK listings | ?last_update_min =2023-01-01 | uk_sanctions |
| regime_name | string | Regime name in UK lists | ?regime_name=Rus sia Regime | uk_sanctions |
| sanctions_ imposed | string | Imposed sanctions types | ?sanctions_impos ed=Asset Freeze | uk_sanctions |
| names_name1 | string | First part of name | ?names_name1=John | uk_sanctions |
| addresses_city | string | City in OFAC/SECO address entries | ?addresses_city= Tehran | ofac_sdn_sanctions, ofac_non_sdn_sanctions |
| uid | string | Unique ID in OFAC/SECO listings | ?uid=36 | ofac_sdn_sanctions, ofac_non_sdn_sanctions |
| sdntype | string | SDN type field | ?sdntype=Entity (sdn) ?sdntype=Individ ual (non_sdn) | ofac_sdn_sanctions, ofac_non_sdn_sanctions |
| programs_p rogram | string | OFAC sanctions program | ?programs_progra m=NPWMD (sdn) ?programs_progra m=SDGT (non_sdn) | ofac_sdn_sanctions, ofac_non_sdn_sanctions |
| akas_first name | string | OFAC alternate name | ?akas_firstname=Mohammed | ofac_sdn_sanctions, ofac_non_sdn_sanctions |
| akas_last name | string | OFAC alternate name | ?akas_lastname=A ERO-CARIBBEAN (sdn) ?akas_lastname=S HEHAB (non_sdn) | ofac_sdn_sanctions, ofac_non_sdn_sanctions |
| date_of_birth_date Of BirthItem | string | Date of birth field from OFAC | ?date_of_birth_d ateofbirthitem=1 975-09-21 | ofac_sdn_sanctions, ofac_non_sdn_sanctions |
| identity_id_number | string | Document number | ?identity_id_num ber=AB123456 | ofac_sdn_sanctions, ofac_non_sdn_sanctions |
| national_country | string | Nationality | ?national_country=Syria | ofac_sdn_sanctions, ofac_non_sdn_sanctions |
| citizenship_country | string | Citizenship | ?citizenship_country=Iran | ofac_sdn_sanctions, ofac_non_sdn_sanctions |
| vesselinfo _vesselFlag | string | Flag of a sanctioned vessel | ?vesselinfo_vess elflag=Panama | ofac_sdn_sanctions |
| location | string | Location name in SECO | ?location=Donetsk | seco_place_sanctions |
| area_variant_type | string | Type of area variant | ?area_variant_type=region | seco_place_sanctions |
| program- key_0_#text | string | Program key from SECO | ?program- key_0_#text=SECO 1234 | seco_program_sanctions |
| origin | string | Origin of SECO entry | ?origin=Swiss Government | seco_program_sanctions |
| ind_addres s_address_ details | string | SECO target address details | ?ind_address_add ress_details=123 Example St | seco_target_sanctions |
| modificati on_modific ation_type | string | Type of modification to SECO target | ?modification_mo dification_type= REMOVAL | seco_target_sanctions |
4.4 Step-by-Step Guide
Step 1: Install and Set Up Postman
- Method: GET
- URL: https://api.datadock.ai/api/v1/globalcomply
Parameters:
- sanctions_agency (This is a required parameter , e.g., ofac_sdn_sanctions, dfat_sanctions)
- name, aliases, citizenship, birth_place
- listing_date_min/max, program, schedule
- format: json | json_download | excel
5. Bulk Data Download API
Endpoint
POST /api/v1/bulk
5.1 Overview
The Bulk Data Download API allows authorized users to download large volumes of data from one of the supported data sources (called workstreams).
Users can apply filters to refine results and choose their preferred download format.
This feature is ideal for clients who need full data exports for analytics, integration, or compliance purposes.
5.2 Supported Workstreams
| Workstream | Description |
|---|---|
| filingflow | SEC filings data such as Form D, 13F-HR, and 13F-NT. |
| globalcomply | Global sanctions and compliance lists from government and international agencies. |
5.3 Authentication
This endpoint requires a valid API key with bulk access permissions.
Header Example:
Authorization: “Bearer <YOUR_API_KEY>”
Content-Type: “application/json”
5.4 Request Parameters
| Field | Type | Required | Description |
|---|---|---|---|
| workstream | String | Yes | The data source to download from. Must be one of: realtystream, filingflow, globalcomply. |
| filters | Object | No | Filters to narrow down your data results. The structure depends on the selected workstream. |
| format | String | No | The download format: "json" (default) or "excel". |
{
"workstream": "globalcomply",
"filters": {
"country": "Belarus",
"sanction_type": "canada_sanctions"
},
"format": "json"
}
{
"workstream": "globalcomply",
"filters": {
"country": "Belarus",
"sanction_type": "canada_sanctions"
},
"format": "excel"
}
5.5 Successful Responses
JSON Download
Status Code: 200 OK
Content-Type: application/json
Header:
Content-Disposition: attachment; filename=<workstream>_data.json
[
{
"country": "Belarus",
"last_name": "Atabekov",
"given_name": "Khazalbek Bakhtibekovich",
"aliases": null,
"schedule": "1, Part 1",
"item": "1",
"dob": "1800-01-01",
"entity": null,
"date_of_listing": "2020-09-28",
"sanctions_origin": "Canada"
}
]
5.6 Excel Download
Status Code: 200 OK
Content-Type:
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Header:
Content-Disposition: attachment; filename<workstream>_data.xlsx
The response body contains an Excel file with the requested dataset.
5.7 Error Responses
| Status Code | Description | Example |
|---|---|---|
| 400 | Invalid or missing parameters | {"error"; "Invalid or missing workstream. Choose from: realtystream, filingflow, globalcomply"} |
| 403 | Download quota exceeded | {"error": "Quota exceeded", "message": "You have reached your download limit for this cycle."} |
| 404 | No data found | {"message": "No data found for the given filters"} |
| 500 | Internal server error | {"error": "Internal server error. Please try again later."} |
5.8 Quota Policy
Each user account has a monthly data download quota based on their subscription plan.
The API measures the total file size of each download and tracks it toward your quota.
If a request exceeds your remaining quota, the system returns a 403 Quota Exceeded error.
Tip:
5.9 Usage Notes
- This endpoint supports bulk data exports for analytics, reporting, and compliance use cases.
- Filtering helps reduce download size and improve response times.
- Available formats: JSON (machine-readable) and Excel (.xlsx) (for spreadsheets and business tools).
- Large downloads may take several seconds to process depending on data volume.
- All downloads are securely logged and tied to your API key for quota tracking.
5.10 Example Use Cases
- iExport recent SEC filings for specific issuers or form types.
- Download the latest global sanctions list for compliance checks.
6. Tips for Success
- Always test your queries with an API testing tool before integrating them into your application.
- Start with simple requests and then use filters to narrow down results.
- Revisit this guide for updates and new features.
7. Error Handling
Error Responses:
- 400 Bad Request: Invalid filter parameters or missing form type.
- 404 Not Found: No records match the given filters.
- 500 Internal Server Error: Database connection failure or other server errors.
8. Contact & Support
For further assistance, refer to the official documentation or contact our support team.
Happy coding!