> GooFuture | Ukraine Sole Trader (FOP) Query Data API

Ukraine Sole Trader (FOP) Query Data API

Plug Ukraine sole trader registry data into cross-border due diligence and risk screening

Covers registration record number, name, business status, registration history, unified registration number, farmer flag and tax registration, with exact lookup, name search, status verification and batch checks.

Turn GB-scale source registry files into auditable compliance data assets

REST API JSON Chinese name mapping 5 status enums
Sole trader registration record
Registration record number 652610
Sole trader Bilous Vasyl Vasylovych
Business status Registered (active)
Farmer (agricultural business) Yes
First registration 2004-09-16
Unified registration number 20070000000000075
Tax registration Taxpayer register (from 2007-12-17)

Why You Need This Data Service

Sole traders (FOP) are the most numerous business entity type in Ukraine. Registry data is published as GB-scale source files with inconsistent encoding, fields and status wording, so using it directly for cross-border due diligence and risk screening requires heavy parsing, translation and cleaning.

🗂️

GB-scale source files are hard to use

The raw registry data is an extremely large flat file with inconsistent encoding and null handling, and names and statuses in the source language, so every integration needs fresh parsing and translation.

🔍

Business status cannot be verified automatically

Statuses such as active, deregistration in progress, deregistered, revoked and bankruptcy proceedings exist as free source text with no unified enums, making manual checks costly and error-prone.

🧾

Registration history and tax data are scattered

First registration date, registration updates, unified registration number, tax registration type and validity dates sit in multi-level fields, making structured comparison difficult.

📚

No batch verification capability

Screening customer, supplier or partner lists in bulk cannot be done record by record — you need a standardized batch verification API.

From source-language registry data to a structured query API

GooFuture turns Ukraine public sole trader registry data into a ready-to-call API through six processing steps.

1
Collect
Sync the Ukraine sole trader registry public data source
2
Decode
Unified encoding conversion, fixing entity escapes and invalid characters
3
Clean
Handle nulls, duplicate records and nested field splitting
4
Chinese
Build Chinese mappings for transliterated names, statuses and termination reasons
5
Normalize
Standardize status enums and unify date, registration number and tax formats
6
Deliver
Serve queries via REST API or Webhook

You do not need to handle source-language decoding or field mapping — query standardized sole trader registry data directly through the API.

API Capabilities

Four core endpoints for different verification scenarios. All return standardized JSON with status normalized into five enums, supporting queries by registration record number, name and status.

API 01

FOP registration record lookup

Look up a full sole trader record by registration record number — name, business status, registration history, unified registration number, farmer flag and tax registration.

GET /v1/ua/fop/{record}
Request Example
curl "https://api.goofuture.com/v1/ua/fop/652610" \
  -H "Authorization: Bearer {api_key}"
Response Example
{
  "record_no": "652610",
  "name": "Bilous·Vasyl·Vasylovych",
  "name_original": "BILOUS VASYL VASYLIOVYCH",
  "status": "Registered(Active)",
  "status_code": "ACTIVE",
  "farmer": true,
  "registration": {
    "first_reg_date": "2004-09-16",
    "unified_no": "20070000000000075"
  },
  "tax": [
    {
      "type": "Taxpayer register",
      "start_date": "2007-12-17",
      "end_date": null
    }
  ]
}
Exact record number lookup Chinese and source text side by side Farmer flag
API 03

Business status verification

Verify a sole trader current status, returning enums such as active, deregistration in progress, deregistered, revoked or bankruptcy proceedings started, together with the deregistration reason.

GET /v1/ua/fop/status?record={record}
Request Example
curl "https://api.goofuture.com/v1/ua/fop/status?record=653792" \
  -H "Authorization: Bearer {api_key}"
Response Example
{
  "record_no": "653792",
  "name": "Strykhar·Anatolii·Ivanovych",
  "name_original": "STRYKAL ANATOLII IVANOVYCH",
  "status": "Deregistered",
  "status_code": "TERMINATED",
  "terminated": {
    "date": "2004-11-04",
    "record_no": "20090060002000059",
    "reason": "Business terminated by decision of the sole trader",
    "reason_original": "Державна реєстрація припинення підприємницької діяльності фізичної особи - підприємця за її рішенням"
  }
}
5 status enums Deregistration reasons in Chinese Auditable status
API 04

Batch sole trader verification

Pass a list of registration record numbers to return business status and registration summary in bulk — for customer list screening and supplier onboarding review.

POST /v1/ua/fop/batch
Request Example
curl -X POST "https://api.goofuture.com/v1/ua/fop/batch" \
  -H "Authorization: Bearer {api_key}" \
  -H "Content-Type: application/json" \
  -d '{"records": ["652610", "653792", "671400"]}'
Response Example
{
  "total": 3,
  "found": 3,
  "results": [
    {
      "record_no": "652610",
      "name": "Bilous·Vasyl·Vasylovych",
      "status": "Registered(Active)",
      "farmer": true
    },
    {
      "record_no": "653792",
      "name": "Strykhar·Anatolii·Ivanovych",
      "status": "Deregistered",
      "terminated_reason": "Business terminated by decision of the sole trader"
    },
    {
      "record_no": "671400",
      "name": "Rundych·Vadym·Oleksiiovych",
      "status": "Deregistered",
      "estate_manager": "Rundych·Vadym·Oleksiiovych",
      "terminated_reason": "Business terminated by court decision(Not related to bankruptcy)"
    }
  ]
}
Bulk list screening Status summary in response Supplier onboarding review

Real-World Use Cases

How companies in different roles and stages use the Ukraine Sole Trader (FOP) Query Data API.

🛡️

Cross-border trade due diligence

Before exporting to or importing from Ukraine, check whether the counterparty sole trader is active or in bankruptcy proceedings, and build a complete counterparty profile.

Role: foreign trade manager · Stage: pre-contract
📋

Risk and compliance screening

Banks and payment institutions screen Ukrainian customer lists in bulk, automatically flagging entities that are deregistering, deregistered or bankrupt to reduce risk.

Role: risk manager · Stage: onboarding review
⚖️

Collections and legal

Establish a debtor business status, deregistration date and reason and identify estate administrators, providing registry evidence for claims and enforcement.

Role: legal specialist · Stage: case handling
🏬

Foreign trade platform integration

Logistics, e-commerce and B2B platforms embed sole trader status verification into merchant onboarding to check entity standing automatically.

Role: product manager · Stage: system integration

Ukraine sole trader registry data coverage

Covers sole trader (FOP) entities registered in Ukraine, with five business statuses: active, deregistration in progress, deregistered, revoked and bankruptcy proceedings.

Millions of records
Registered entity records
5
Business status enums
9
Core registry fields
Quarterly
Update frequency
Data dimensions
Entity information (registration record number, name, farmer flag)
Business status (active, deregistering, deregistered, revoked, bankruptcy)
Registration history (first registration, updates, unified registration number)
Termination information (deregistration date, number, reason)
Tax registration (taxpayer register and validity dates)
Dimensions are ordered by field coverage. Covers sole trader records registered in Ukraine, including active, deregistering, deregistered, revoked and bankruptcy proceedings. As of: August 2026. Static snapshot shown to illustrate coverage only.

Data Quality & Differentiators

GooFuture cleans source-language sole trader registry data into directly queryable structured data, lowering integration and maintenance cost.

Standardized status enums

Map source-language status descriptions into five enums — active, deregistering, deregistered, revoked, bankruptcy started — while keeping the source text for audit review.

Five enums

Chinese name mapping

Provides Chinese and Latin transliterations of sole trader names while keeping the source text, so Chinese teams can use and review it directly.

Bilingual

Structured registration history

Split history fields such as first registration, registration updates and unified registration number, unify date formats and support filtering by registration date range.

Consistent format

Termination reasons in Chinese

Translate and classify deregistration reasons (own decision, simplified procedure, court decision, declared missing and more) so risk rules can reference them directly.

Classified reasons

Status change tracking

Track sole trader business status and registration changes with Webhook pushes so verified entity data does not go stale.

Change tracking

Three-Step Onboarding

From consultation to production queries in as little as a few hours.

1

Contact a consultant

Describe your cross-border due diligence or risk screening needs and confirm the data scope required (record number, name, status, batch size and more).

2

Confirm the plan

Both sides agree on endpoint scope, call volume, concurrency and update frequency. Webhook or CSV batch delivery is agreed at this stage.

3

Start Querying

Get an API key and docs, then query over standard REST. Technical support is provided during integration so results can be used directly in your systems.

4

Ongoing maintenance

Registry data syncs quarterly and business status changes are pushed via Webhook. Your consultant keeps tracking data quality and API stability.

Quick Start Example
# Query an FOP registration record
curl "https://api.goofuture.com/v1/ua/fop/652610" \
  -H "Authorization: Bearer {api_key}"

# Verify business status
curl "https://api.goofuture.com/v1/ua/fop/status?record=653792" \
  -H "Authorization: Bearer {api_key}"

# Batch-verify sole traders
curl -X POST "https://api.goofuture.com/v1/ua/fop/batch" \
  -H "Authorization: Bearer {api_key}" \
  -H "Content-Type: application/json" \
  -d '{"records": ["652610", "653792", "671400"]}'

Choose the Right Plan

From single-record verification to batch due diligence, from low-frequency calls to high-concurrency integration — four plans.

Basic

Contact a consultant
  • Monthly requests: 5,000
  • API scope: exact record number lookup
  • Rate limit: 1 QPS
  • Monitoring: —
  • Delivery: REST API
  • Support: email support
Talk to Us

Professional

Contact a consultant
  • Monthly requests: 100,000
  • API scope: all core endpoints + batch verification
  • Rate limit: 5 QPS
  • Monitoring: status-change push
  • Delivery: REST API + Webhook + CSV
  • Support: dedicated technical consultant
Talk to Us

Enterprise

Contact a consultant
  • Monthly requests: custom
  • API scope: all + custom endpoints
  • Rate limit: high concurrency
  • Monitoring: custom
  • Delivery: REST API + Webhook + CSV
  • Support: enterprise-grade SLA
Talk to Us

FAQ

Common questions about data scope, update frequency, API capabilities and pricing.

Which sole traders are covered?

Millions of records from the Ukrainian sole trader (FOP) register, covering active, deregistering, deregistered, revoked and bankruptcy-started entities. Each record includes registration record number, name, business status, registration history, unified registration number, farmer flag and tax registration.

Why not query the public Ukrainian company registry data directly?

Raw data is published as GB-scale flat files with inconsistent encoding, field naming and null handling, names and statuses in the source language, and no query interface by registration record number or name. GooFuture decodes, cleans, translates and structures it so it plugs straight into due diligence and verification workflows.

Which query filters are supported?

Exact registration record number lookup, name search (Chinese or source language), business status verification and batch checks. Status is unified into five enums: active, deregistering, deregistered, revoked and bankruptcy started.

How often is it updated?

Registry data updates quarterly. Business status changes (new deregistration, entering bankruptcy) are pushed to Webhook subscribers. Exact frequency is agreed when confirming the plan.

Can it integrate with our existing ERP or SaaS platform?

Yes. The REST API returns standardized JSON with fixed fields and unified enums. It supports Webhook update pushes and batch delivery in CSV or Excel on request.

Does the data include tax information?

The core API includes tax registration type (such as taxpayer register) and validity dates. Detailed tax filing data is out of scope — discuss extension needs when finalizing the plan.

How is pricing calculated?

Pricing is based on monthly request volume. Basic suits low-frequency single-record verification, Standard adds name search and status verification, and Professional and Enterprise support higher concurrency, batch checks, Webhooks and custom integration. Contact a consultant for a specific plan.

Does the data cover countries outside Ukraine?

Data currently covers only sole traders (FOP) registered in Ukraine. Entity registry data for other countries and regions is out of scope.

Plug Ukraine sole trader registry data into due diligence and risk control

From business status to registration history, from unified registration number to tax registration — a complete compliance data foundation for Ukrainian entities.