Seattle Business License Tax Certificates avatar

Seattle Business License Tax Certificates

Pricing

from $13.40 / 1,000 registry records

Go to Apify Store
Seattle Business License Tax Certificates

Seattle Business License Tax Certificates

One record per active Seattle business-licence tax certificate (legal + trade name, ownership type, NAICS activity, licence start date, address, city account number, UBI) from the keyless Seattle open-data resource.

Pricing

from $13.40 / 1,000 registry records

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Share

🔔 Seattle Business License Tax Certificates

One record per active Seattle business-licence tax certificate (legal + trade name, ownership type, NAICS activity, licence start date, address, city account number, UBI) from the keyless Seattle open-data resource. Certificate fields carried verbatim; nulls preserved.

Public, robots-honoured.

Output is one seattle_business_license row per result; billing is pay-per-event, the value event being one registry record (a $0.02 start fee per run, then $0.02 per registry record). Source: data.seattle.gov.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

Who buys this

Buyers usually search for Seattle business license or Seattle businesses.

  • Sales and lead-generation teams building lists from Seattle business license.
  • KYB, onboarding and compliance teams checking Seattle businesses.
  • Market researchers and data teams that need the official record as rows.

📊 Sample Output

Seattle Business License Tax Certificates sample output — a table of real registry record rows (business_legal_name, trade_name, ownership_type, naics_description) from run WArfxVBOlUpwUvaIM on build 0.1.6

Real rows from run WArfxVBOlUpwUvaIM on build 0.1.6 (2026-09-18), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

business_legal_nametrade_nameownership_typenaics_descriptionlicense_start_datestreet_address
ABDURAKHMANOV RASULRASUL ABDURAKHMANOVSole proprietorshipLimousine Service20140814706 UNION ST # 409
AHMED MUSTAFE FMUSTAFE F AHMEDSole proprietorshipAll Other Transit and Ground Passenger Transportation2014110714203 42ND AVE S # 221
BUI PHUONGBUI PHUONGSole proprietorshipBed-and-Breakfast Inns201908272324 1ST AVE #313
CRUZ BRENDAN JPHENOMENAL PHILLIESole proprietorshipRetail Bakeries202208014130 PALATINE AVE N
DAVID ANTHONY LEWIS PSDAVID ANTHONY LEWIS PSCorporationAll Other Miscellaneous Schools and Instruction202202038707 16TH AVE SW
GATES FOUNDATION TRUSTGATES FOUNDATION TRUSTOtherGrantmaking Foundations20000101500 5TH AVE N
INDERJIT TAXIINDERJIT TAXISole proprietorshipTaxi and Ridesharing Services202507302464 S 296TH PL
JUGRAJ BRARJUGRAJ BRARSole proprietorshipAll Other Transit and Ground Passenger Transportation2014121030036 65TH AVE S

The run finished with the status message: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • record_type (string) — e.g. seattle_business_license
  • business_legal_name (string/null) — e.g. ABDURAKHMANOV RASUL
  • trade_name (string/null) — e.g. RASUL ABDURAKHMANOV
  • ownership_type (string/null) — e.g. Sole proprietorship
  • naics_code (string/null) — e.g. 485320
  • naics_description (string/null) — e.g. Limousine Service
  • license_start_date (string/null) — e.g. 20140814
  • street_address (string/null) — e.g. 706 UNION ST # 409
  • city (string/null) — e.g. SEATTLE
  • state (string/null) — e.g. WA
  • zip (string/null) — e.g. 98101
  • business_phone (string/null) — e.g. 2062579788
  • city_account_number (string/null) — e.g. 0007748490686809
  • ubi (string/null) — e.g. 6044995720010001
  • source (string/null) — e.g. seattle-business-license-tax-certificates
  • release_date (string/null) — null in every sample row
  • source_url (string/null) — e.g. https://data.seattle.gov/resource/wnbq-64tb.json
  • observed_at (string/null) — e.g. 2026-09-18T20:09:10Z
  • terminal (string/integer/null) — null in every sample row
  • reported_total (string/integer/null) — null in every sample row
  • raw_seen (string/integer/null) — null in every sample row
  • duplicates (string/integer/null) — null in every sample row
  • unique_found (string/integer/null) — null in every sample row
  • delivered (string/integer/null) — null in every sample row
  • scope (string/integer/null) — null in every sample row
  • note (string/integer/null) — null in every sample row
  • license (string/integer/null) — null in every sample row
  • attribution (string/integer/null) — null in every sample row

✅ What you get

  • record_type (string) — e.g. seattle_business_license
  • business_legal_name (string/null) — e.g. ABDURAKHMANOV RASUL
  • trade_name (string/null) — e.g. RASUL ABDURAKHMANOV
  • ownership_type (string/null) — e.g. Sole proprietorship
  • naics_code (string/null) — e.g. 485320
  • naics_description (string/null) — e.g. Limousine Service
  • license_start_date (string/null) — e.g. 20140814
  • street_address (string/null) — e.g. 706 UNION ST # 409
  • city (string/null) — e.g. SEATTLE
  • state (string/null) — e.g. WA
  • zip (string/null) — e.g. 98101
  • business_phone (string/null) — e.g. 2062579788
  • city_account_number (string/null) — e.g. 0007748490686809
  • ubi (string/null) — e.g. 6044995720010001
  • source (string/null) — e.g. seattle-business-license-tax-certificates
  • release_date (string/null) — null in every sample row
  • source_url (string/null) — e.g. https://data.seattle.gov/resource/wnbq-64tb.json
  • observed_at (string/null) — e.g. 2026-09-18T19:44:20Z
  • terminal (string/integer/null) — null in every sample row
  • reported_total (string/integer/null) — null in every sample row
  • raw_seen (string/integer/null) — null in every sample row
  • duplicates (string/integer/null) — null in every sample row
  • unique_found (string/integer/null) — null in every sample row
  • delivered (string/integer/null) — null in every sample row
  • scope (string/integer/null) — null in every sample row
  • note (string/integer/null) — null in every sample row
  • license (string/integer/null) — null in every sample row
  • attribution (string/integer/null) — null in every sample row

What you get

One registry_record per entity, deduplicated on the source-native id. Fields the source does not publish are honest null. A run_receipt row carries the source URL, scope, reconciliation counts, and delivered/duplicate totals.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
"maxRecords": 50
}

The sample run charged exactly: 2 × $0.02 apify-actor-start + 50 × $0.02 registry_record = $1.04 on the Free tier — every delivered row was billed. If you leave maxRecords out, the run delivers at most 5000 rows (the schema default); pass a number up to 500000 for a bigger export. An explicit value is always honoured up to that maximum.

2. A smaller, narrowed run

{
"maxRecords": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02).

3. A full-size run

{
"maxRecords": 5000
}

Up to 5000 rows — about $100.02 on the Free tier ($0.02 start + 5000 × $0.02) if the source has that many; maxRecords goes up to 500000.

4. A filtered run

{
"maxRecords": 10,
"fieldMatch": {
"business_legal_name": "pure madness"
}
}

Seattle licences whose legal name contains pure madness; the source applies this filter before paging and before the maxRecords cap, so a match deep in the dataset is found, the reconciled count is the matched count, and only delivered matches are billed. A confirmed no-match ends EMPTY_SELECTION with nothing charged.

🧾 JSON sample record

One real record from run WArfxVBOlUpwUvaIM, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_type": "seattle_business_license",
"business_legal_name": "ABDURAKHMANOV RASUL",
"trade_name": "RASUL ABDURAKHMANOV",
"ownership_type": "Sole proprietorship",
"naics_code": "485320",
"naics_description": "Limousine Service",
"license_start_date": "20140814",
"street_address": "706 UNION ST # 409",
"city": "SEATTLE",
"state": "WA",
"zip": "98101",
"business_phone": "2062579788",
"city_account_number": "0007748490686809",
"ubi": null,
"source": "seattle-business-license-tax-certificates",
"release_date": null,
"source_url": "https://data.seattle.gov/resource/wnbq-64tb.json",
"observed_at": "2026-09-18T20:09:10Z"
}

🔧 How it works

Source. The actor reads data.seattle.gov — endpoints: https://data.seattle.gov/resource/wnbq-64tb.json. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent. Pacing: CRAWL_DELAY=0.0.

Charging. Each registry record is charged at the moment it is pushed (registry_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

🔧 How it works

How it behaves

Rows are paged from the Seattle Socrata resource (:id order, $limit/$offset) and count(*) reconciled. Fields copied verbatim. Streaming, bounded to maxRecords; full-scope :id-ordered, memory bounded.

Source

https://data.seattle.gov/resource/wnbq-64tb.json

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Registry Record (registry_record)$0.02$0.018$0.016$0.0134

Worked at the live Free-tier price:

  • 8 registry records: $0.02 start + 8 × $0.02 = $0.18
  • 25 registry records: $0.02 start + 25 × $0.02 = $0.52
  • 5000 registry records: $0.02 start + 5000 × $0.02 = $100.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50. maxRecords is a hard ceiling on what is delivered and billed, never a target.

This actor reads public, logged-out pages and feeds published by data.seattle.gov. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (data.seattle.gov) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 5000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other NexGen Watch actors actors?
A: Same output shape and billing model; this one covers data.seattle.gov. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source (CRAWL_DELAY=0.0) and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

  • Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
  • Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
  • Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
  • Poland KRS Company Registry — One record per requested KRS number — company name, legal form, REGON, NIP, address and registration dates from the official current extract. This is…
  • Poland VAT Whitelist Verifier — One vat_check verdict per queried identifier against Poland's official Ministry of Finance VAT whitelist (Wykaz podatników VAT) — keyless, logged-out…
  • ESMA Prospectus Register Check — One prospectus_check verdict per issuer name you submit, resolved against ESMA's official Prospectus Register (the EU register of approved prospectus…
  • Slovakia Public-Sector Partners Register — One record per registered public-sector partner from the official RPVS OData — official ID, business name, validity dates, and beneficial owners when…
  • Spain AEMPS Medicines Registry (CIMA) — One record per authorized medicine from the official CIMA REST API — national code, name, laboratory, authorization status; presentation/route/docume…
  • Spain BOE Official Records — One structured official_notice per entry in the Boletín Oficial del Estado daily summary, from the official BOE open-data API — keyless, logged-out
  • 🏢 About NexGen Watch — NexGen Watch is a catalog of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.