ESG Supply Chain Auditor avatar

ESG Supply Chain Auditor

Pricing

Pay per usage

Go to Apify Store
ESG Supply Chain Auditor

ESG Supply Chain Auditor

Provide a supplier name and optional country/industry filters. The Actor writes one normalized dataset item per audit, including legal-entity resolution and ESG/risk flags.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

jts

jts

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

What this Actor does

Provide a supplier name and optional country/industry filters. The Actor writes one normalized dataset item per audit, including legal-entity resolution and ESG/risk flags.

Input example

{
"supplierName": "Acme Manufacturing",
"supplierCountry": "US",
"industryCodes": [
"332710"
],
"riskChecks": [
"ofac",
"epa-violations",
"forced-labor-cbp"
]
}

Input fields

Provide a supplier name plus optional country/industry filters. The Actor writes one normalized dataset item per audit.

  • supplierName (string, user input): Supplier company name to resolve.
  • supplierCountry (string, user input): ISO2 country code to scope the registry search.
  • industryCodes (array, user input): NAICS industry codes.
  • riskChecks (array, user input): Risk source checks to enable. Defaults to all.
  • apiToken (string, user input): Optional OpenCorporates API token (secret) for higher rate limits.
  • 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 ESG_SUPPLY_CHAIN_AUDITOR_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