NYC DCWP Business Licence Registry avatar

NYC DCWP Business Licence Registry

Pricing

from $13.40 / 1,000 registry records

Go to Apify Store
NYC DCWP Business Licence Registry

NYC DCWP Business Licence Registry

One business_licence_record per DCWP licence: licence number, business + DBA name, category, type, status, creation/expiration dates, contact phone, and full address, from the keyless Socrata API.

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

2 days ago

Last modified

Categories

Share

πŸ”” NYC DCWP Business Licence Registry

One business_licence_record per DCWP licence: licence number, business + DBA name, category, type, status, creation/expiration dates, contact phone, and full address, from the keyless Socrata API.

One structured registry_record per record from the NYC Open Data DCWP licences resource (Socrata w7w3-xahh, ~69,885 rows). Public, logged-out, robots-honoured.

Output is one business_licence_record 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.cityofnewyork.us.

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

πŸ“Š Sample Output

NYC DCWP Business Licence Registry sample output β€” a table of real registry record rows (license_number, business_name, business_category, license_type) from run UFhSVR9GnDH4qzbZF on build 0.1.5

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

license_numberbusiness_namebusiness_categorylicense_typelicense_creation_datelicense_expiration_date
0002902-DCAGEM FINANCIAL SERVICES, INC.PawnbrokerPremises2007-04-18T00:00:00.0002027-04-30T00:00:00.000
0010669-DCASAYYED, IQBALNewsstandPremises2002-03-25T00:00:00.0002028-03-31T00:00:00.000
0010699-DCAKALOGIANNAKIS, MARINOSNewsstandPremises2002-05-14T00:00:00.0002028-03-31T00:00:00.000
0010971-DCAKAUFMAN, MARILYNNewsstandPremises1999-02-12T00:00:00.0002024-03-31T00:00:00.000
0010985-DCATOM, SIK PUINewsstandPremises1999-02-11T00:00:00.0002024-03-31T00:00:00.000
0011544-DCAOLSEN NEWS CORP.NewsstandPremises1999-02-12T00:00:00.0002026-03-31T00:00:00.000
0011671-DCADESAI, INDUBEN KNewsstandPremises1999-02-11T00:00:00.0002028-03-31T00:00:00.000
0016371-DCAJAMES ROBINSON, INC.Secondhand Dealer - GeneralPremises2003-10-31T00:00:00.0002027-07-31T00:00:00.000

The run finished with the status message: CAPPED: delivered 50 of 51 unique rows (maxRecords=50). 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. business_licence_record
  • license_number (string/null) β€” e.g. 0002902-DCA
  • business_name (string/null) β€” e.g. GEM FINANCIAL SERVICES, INC.
  • dba_trade_name (string/null) β€” e.g. GEM PAWNBROKERS
  • business_category (string/null) β€” e.g. Pawnbroker
  • license_type (string/null) β€” e.g. Premises
  • license_status (string/null) β€” e.g. Active
  • license_creation_date (string/null) β€” e.g. 2007-04-18T00:00:00.000
  • license_expiration_date (string/null) β€” e.g. 2027-04-30T00:00:00.000
  • contact_phone (string/null) β€” e.g. 7182371166
  • address (string/null) β€” e.g. 608 8TH AVE
  • city (string/null) β€” e.g. NEW YORK
  • state (string/null) β€” e.g. NY
  • zip (string/null) β€” e.g. 10018
  • borough (string/null) β€” e.g. Manhattan
  • source (string/null) β€” e.g. nyc-dcwp-business-licence-registry
  • release_date (string/null) β€” null in every sample row
  • source_url (string/null) β€” e.g. https://data.cityofnewyork.us/resource/w7w3-xahh.json
  • observed_at (string/null) β€” e.g. 2026-09-18T05:50:14Z
  • 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

What you get

One registry_record per entity, deduplicated on the source-native id. Fields the source does not publish for a row are honest null. A run_receipt row carries the source URL, any reported total, and the delivered/duplicate counts.

βš™οΈ Sample inputs

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

{
"maxRecords": 50
}

The sample run charged exactly: 1 Γ— $0.02 apify-actor-start + 50 Γ— $0.02 registry_record = $1.02 on the Free tier β€” every delivered row was billed.

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 (the schema default for maxRecords) β€” about $100.02 on the Free tier ($0.02 start + 5000 Γ— $0.02) if the source has that many.

🧾 JSON sample record

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

{
"record_type": "business_licence_record",
"license_number": "0002902-DCA",
"business_name": "GEM FINANCIAL SERVICES, INC.",
"dba_trade_name": "GEM PAWNBROKERS",
"business_category": "Pawnbroker",
"license_type": "Premises",
"license_status": "Active",
"license_creation_date": "2007-04-18T00:00:00.000",
"license_expiration_date": "2027-04-30T00:00:00.000",
"contact_phone": "7182371166",
"address": "608 8TH AVE",
"city": "NEW YORK",
"state": "NY",
"zip": "10018",
"borough": "Manhattan",
"source": "nyc-dcwp-business-licence-registry",
"release_date": null,
"source_url": "https://data.cityofnewyork.us/resource/w7w3-xahh.json",
"observed_at": "2026-09-18T05:50:14Z"
}

πŸ”§ How it works

Source. The actor reads data.cityofnewyork.us β€” endpoints: https://data.cityofnewyork.us/resource/w7w3-xahh.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.

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 behaves

Keyless Socrata $limit/$offset pagination. Bound the run with maxRecords; raise it for the full register. maxRecords caps the count. Duplicates, outages, and schema drift charge nothing.

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.02$0.02$0.01

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: CAPPED: delivered 50 of 51 unique rows (maxRecords=50). 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.cityofnewyork.us. 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.cityofnewyork.us) 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.cityofnewyork.us. 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 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.

⭐ 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.