Vz APIrekvizitai.vz.lt ↗
Search Lithuanian companies and retrieve contact details, financials, and multi-year revenue history from rekvizitai.vz.lt via a structured JSON API.
What is the Vz API?
This API provides structured access to Lithuanian company data from rekvizitai.vz.lt across 3 endpoints. Use search_companies to filter by name, registration code, industry, or location, then retrieve full contact details and financials with get_company_details and get_company_financials. Response fields include revenue, net profit, employee count, manager name, VAT code, and year-by-year breakdowns of turnover, equity, liabilities, and assets.
curl -X GET 'https://api.parse.bot/scraper/b89a25ec-6709-4f33-8f08-47f852cf665e/search_companies?name=Telia&page=1&limit=10&order=1&query=UAB&offset=0' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace rekvizitai-vz-lt-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.rekvizitai_lithuanian_company_directory_api import Rekvizitai, Order
client = Rekvizitai()
# Search for companies by name with revenue ordering
for company in client.companysummaries.search(name="Telia", order=Order.REVENUE_DESC, limit=5):
print(company.name, company.slug, company.address)
# Get full company details via the summary's details() navigation
summary = client.companysummary(slug="telia_global_services_lithuania")
detail = summary.details()
print(detail.name, detail.company_code, detail.revenue, detail.employees)
# Access financial history as a sub-resource of the detail
report = detail.financials.get()
print(report.years, report.slug)
for metric, values in report.financials.items():
print(metric, values)Search for Lithuanian companies by name, company code, keyword, industry, or location. Returns paginated results with company name, slug, address, and activities. Supports ordering by relevance, name, or revenue. Pagination is 1-based.
| Param | Type | Description |
|---|---|---|
| name | string | Company name to search for. |
| page | integer | Page number for pagination (1-based). |
| order | string | Result ordering. |
| industry | string | Industry filter (Lithuanian industry name). |
| location | string | Location filter (city or municipality name in Lithuanian). |
| search_word | string | General keyword to search across company records. |
| company_code | string | Company registration code to search for. |
{
"type": "object",
"fields": {
"page": "integer current page number",
"companies": "array of company objects with name, slug, url, address, activities",
"total_count": "integer total number of matching companies, or null if not displayed"
},
"sample": {
"data": {
"page": 1,
"companies": [
{
"url": "https://rekvizitai.vz.lt/imone/telia_global_services_lithuania/",
"name": "Telia Global Services Lithuania",
"slug": "telia_global_services_lithuania",
"address": "Saltoniškių g. 7A, LT-08126 Vilnius.",
"activities": "Veiklos sritys: telekomunikacijos, ryšio priemonės; finansai."
}
],
"total_count": 10
},
"status": "success"
}
}About the Vz API
Search and Identify Companies
search_companies accepts up to seven parameters — name, company_code, search_word, industry, location, order, and page — and returns a paginated list of matching Lithuanian companies. Each result includes the company's name, slug, url, address, and activities. The order parameter controls result ranking: relevance, alphabetical (A-Z or Z-A), or revenue descending. total_count is returned when the source exposes it, and may be null for some queries.
Company Profile Details
get_company_details takes a slug from search results and returns a full company record: email, phones, address, website, manager, vat_code, employees, revenue, and net_profit. Revenue and profit fields include the currency and the reporting year inline as a string. The endpoint covers the most recently reported figures rather than a full time series — use get_company_financials for historical depth.
Multi-Year Financial History
get_company_financials returns a financials object keyed by Lithuanian metric names (turnover, profit/loss, profitability, equity, liabilities, assets), where each metric maps to year-to-value pairs. The years array lists every year present in the dataset for that company. This makes it straightforward to build trend views or compare performance across reporting periods without additional requests.
The Vz API is a managed, monitored endpoint for rekvizitai.vz.lt — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when rekvizitai.vz.lt changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official rekvizitai.vz.lt API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Verify a Lithuanian supplier's registration code, VAT code, and registered address before onboarding.
- Screen potential business partners by reviewing manager name, employee count, and recent revenue from get_company_details.
- Build a company credit-risk model using multi-year equity, liabilities, and net profit trends from get_company_financials.
- Filter companies by industry and location to build targeted B2B prospect lists via search_companies.
- Track year-over-year revenue and profitability changes for a portfolio of Lithuanian entities.
- Enrich a CRM with verified contact data including phone numbers, website, and email for Lithuanian companies.
- Identify the largest companies in a specific Lithuanian municipality by sorting search results by revenue descending.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does rekvizitai.vz.lt offer an official developer API?+
What does get_company_financials actually return, and how many years of data are included?+
financials object whose keys are Lithuanian metric names (turnover, profit/loss, profitability, equity, liabilities, assets). Each key maps to an object of year-to-value pairs. The years array lists every covered year. The number of years varies by company depending on how long the entity has filed; there is no fixed cutoff.Can I search by VAT code rather than company registration code?+
search_companies endpoint accepts a company_code parameter for the registration code. VAT code lookup as a dedicated search parameter is not currently supported. The VAT code is returned as a field (vat_code) in get_company_details once you have the slug. You can fork the API on Parse and revise it to add VAT-code-based search if the source supports that query.Does the API return shareholder or ownership structure data?+
Is total_count always available in search_companies results?+
total_count field is returned as an integer when the source displays a result count, but it can be null for certain queries where that count is not surfaced. Plan pagination logic to handle a null value gracefully.