Business Bankruptcy Docket Monitor
Under maintenancePricing
from $0.01 / 1,000 results
Business Bankruptcy Docket Monitor
Under maintenanceProvide a company name (or EIN) plus optional chapter and since-date filters. The Actor writes one normalized dataset item per matching federal bankruptcy docket.
Pricing
from $0.01 / 1,000 results
Rating
0.0
(0)
Developer
jts
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
18 days ago
Last modified
Categories
Share
What this Actor does
Provide a company name (or EIN) plus optional chapter and since-date filters. The Actor writes one normalized dataset item per matching federal bankruptcy docket.
Input example
{"companyName": "FTX Trading","ein": "12-3456789","chapter": "11","sinceDate": "2024-01-01","maxResults": 50}
Input fields
Provide a company name (or EIN), optional chapter and since-date filters, plus a CourtListener API token via clientToken.
companyName(string, user input): Debtor / company name (full or partial).ein(string, user input): Optional Employer Identification Number.chapter(string, user input): Bankruptcy chapter filter (7, 11, 13, all).sinceDate(string, user input): ISO date (YYYY-MM-DD). Only dockets filed on or after this date.maxResults(integer, user input): Maximum dockets to return.clientToken(string, user input): CourtListener API token (treated as a secret). Get one at https://www.courtlistener.com/profile/api/.apiBaseUrl(string, optional override): Optional upstream API base URL override for local or staging QA.
Output dataset
Each successful upstream response is written to the default dataset.
input: Original input value submitted to the upstream API.result: Full upstream API response.
Developer notes
Set BUSINESS_BANKRUPTCY_DOCKET_MONITOR_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API.
Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json.
For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.
Run locally
$apify run
Deploy
$apify push