new-jersey-business-registry-lookup-and-name-checker · diff

git:20261102.e1dc710 to git:20261104.94103e0

47 added, 45 removed. Audit A to A.

---

name: new-jersey-business-registry-lookup-and-name-checker

- description: "Use the New Jersey Business Registry Lookup & Name Checker actor to pull business entities from the state registry and return entity name, status, formed date, agent, city, URL. Use when the user needs a public-data lead list, a local business export, or a repeatable outbound dataset without maintaining a scraper."

+ description: "Look up New Jersey registered businesses by name, keyword or entity ID, and check whether a candidate business name is available for a new filing. Returns entity ID, entity type, city and incorporation date. Output fields: businessName, entityTypeAbbr, entityTypeFull, city, incorporatedDate and more, as JSON rows. Use when the user asks for New Jersey business entity search, business name availability check, or a CSV/JSON export of public NJ business registry data."

---

# New Jersey Business Registry Lookup & Name Checker

- Pull **business entities** from **the state registry** with the public Scraper Finder actor.

+ Look up New Jersey registered businesses by name, keyword or entity ID, and check whether a candidate business name is available for a new filing. Returns entity ID, entity type, city and incorporation date.

- - Actor: https://apify.com/vexaloom-labs/new-jersey-business-registry-lookup-and-name

- - Actor ID: `vexaloom-labs~new-jersey-business-registry-lookup-and-name`

- - n8n workflow: https://github.com/bolvein-firex/scraping-n8n-workflows/blob/main/workflows/new-jersey-business-registry-lookup-and-name-checker.json

+ - Actor: https://apify.com/vexaloom-labs/new-jersey-business-registry-lookup-and-name (ID `vexaloom-labs~new-jersey-business-registry-lookup-and-name`)

+ - n8n workflow for the same Actor: https://github.com/bolvein-firex/scraping-n8n-workflows/blob/main/docs/new-jersey-business-registry-lookup-and-name-checker.md

- Example input: `references/example-input.json`

- Input schema: `references/input-schema.json`

+ - Output fields: `references/output-fields.json`

+ Short video breakdown:

+ - [Stop checking business filings one name at a time](https://www.youtube.com/shorts/tGV77V4rMqk)

## When to use

Use this skill when the user wants:

- - a local business or B2B lead list with public contact details

- - a repeatable dataset instead of manual copy-paste

- - a CSV/JSON output for a CRM, sheet, dashboard, or agent

- - a scheduled refresh of public data

+ - New Jersey business entity search

+ - business name availability check

+ - a repeatable export of public NJ business registry data as CSV or JSON

- Do not use it for private, login-protected, or paywalled data.

+ Do not use it for private, login-protected or paywalled data.

## What it returns

- - entity name

- - status

- - formed date

- - agent

- - city

- - URL

+ One JSON row per result. Columns from the Actor's dataset schema:

+ - `businessName`: Business Name

+ - `entityId`: Entity Id

+ - `entityTypeAbbr`: Entity Type Abbr

+ - `entityTypeFull`: Entity Type Full

+ - `city`: City

+ - `incorporatedDate`: Incorporated Date

+ - `incorporatedMonth`: Incorporated Month

+ - `isAvailable`: Is Available

+ - `documentCount`: Document Count

+ All 10 declared fields: `references/output-fields.json`.

## Inputs

|---|---|---|---|---|

+ | `keywordSearches` | array | no | [] | One or more keyword phrases (mode=byKeyword). Each phrase is split into words, and every word must appear in the business name; up to 5 words per phrase and 20 phrases. |

+ | `entityIds` | array | no | [] | Exact 10-digit New Jersey entity IDs (mode=byEntityId, documents). Invalid IDs are reported in the run status instead of being dropped silently. Up to 200 IDs. |

+ | `entityTypes` | array | no | [] | Keep only these New Jersey entity types. Empty means no filter. Filters run on every page, not only after the 500-row display cap. |

Example:

```json

{

"searchQuery": "roofing",

"status": "Active",

"maxResults": 500

}

```

## Run it

- Set `APIFY_TOKEN` in your environment, then call the synchronous endpoint for small and medium runs:

+ Set `APIFY_TOKEN`, then call the synchronous endpoint for small and medium runs (it waits up to 300 seconds):

```bash

- curl -s -X POST "https://api.apify.com/v2/acts/vexaloom-labs~new-jersey-business-registry-lookup-and-name/run-sync-get-dataset-items?token=$APIFY_TOKEN" \

+ curl -s -X POST "https://api.apify.com/v2/acts/vexaloom-labs~new-jersey-business-registry-lookup-and-name/run-sync-get-dataset-items" \

+ -H "Authorization: Bearer $APIFY_TOKEN" \

-H "Content-Type: application/json" \

- -d @references/example-input.json

+ -d @references/example-input.json > output.json

```

- For large runs, start an async run and read the dataset:

+ Or with Node 18+: `node scripts/run.mjs [input.json]`.

- ```bash

- RUN=$(curl -s -X POST "https://api.apify.com/v2/acts/vexaloom-labs~new-jersey-business-registry-lookup-and-name/runs?token=$APIFY_TOKEN" \

- -H "Content-Type: application/json" \

- -d @references/example-input.json | jq -r '.data.id')

+ For large runs, start an async run and read its dataset when it finishes:

- curl -s "https://api.apify.com/v2/actor-runs/$RUN?token=$APIFY_TOKEN" | jq '.data.status'

- curl -s "https://api.apify.com/v2/datasets/$(curl -s "https://api.apify.com/v2/actor-runs/$RUN?token=$APIFY_TOKEN" | jq -r '.data.defaultDatasetId')/items?token=$APIFY_TOKEN&format=json" > output.json

+ ```bash

+ RUN=$(curl -s -X POST "https://api.apify.com/v2/acts/vexaloom-labs~new-jersey-business-registry-lookup-and-name/runs" \

+ -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \

+ -d @references/example-input.json)

+ RUN_ID=$(echo "$RUN" | jq -r '.data.id'); DATASET=$(echo "$RUN" | jq -r '.data.defaultDatasetId')

+ curl -s "https://api.apify.com/v2/actor-runs/$RUN_ID?waitForFinish=60" -H "Authorization: Bearer $APIFY_TOKEN" | jq -r '.data.status'

+ curl -s "https://api.apify.com/v2/datasets/$DATASET/items?format=json" -H "Authorization: Bearer $APIFY_TOKEN" > output.json

```

- Or import the n8n workflow: https://github.com/bolvein-firex/scraping-n8n-workflows/blob/main/workflows/new-jersey-business-registry-lookup-and-name-checker.json

## Cost and limits

- - Billing is per Apify actor run and per dataset item. Check the actor page for current pricing.

- - `run-sync-get-dataset-items` has a request timeout. Use the async pattern for large jobs.

- - Respect rate limits and the target site's terms.

+ - Apify bills the Actor's usage on your account; the Actor's Pricing tab shows the current price.

+ - Keep the limit in the input small for a first run.

## Guardrails

- - Public data only. Do not use cookies, sessions, or private account data.

- - Do not use the output for spam, harassment, or unlawful discrimination.

- - Verify local law and the target site's terms before running at scale.

- - Demo rows in the Scraper Finder video are illustrative.

- ## Files

- - `scripts/run.mjs` - minimal Node runner using `APIFY_TOKEN`

- - `references/input-schema.json` - full actor input schema

- - `references/example-input.json` - starter input

+ - Public data only. Do not pass cookies, sessions or private account data.

+ - Do not use the output for spam, harassment or unlawful discrimination.

+ - Check the target site's terms and local law before running at scale.