API reference / Developers
Automation metadata API
Automation routes expose cached products, triggers, records, and actions such as tender search, recall search, and dataset diff when configured.
Endpoint
/api/public/automation/productsLists automation products and metadata.
- Access
- Automation marketplace access may be required for protected products
- Freshness
- Cached public-safe artifact. Check product cadence for source refresh expectations.
curl -sS https://zentrafoundry.com/api/public/automation/productsconst response = await fetch('https://zentrafoundry.com/api/public/automation/products', {
method: 'GET',
headers: { 'Accept': 'application/json' }
});
const payload = await response.json();import requests
response = requests.get('https://zentrafoundry.com/api/public/automation/products', headers={'Accept': 'application/json'})
payload = response.json()Purpose
Automation routes expose cached products, triggers, records, and actions such as tender search, recall search, and dataset diff when configured.
Public and auth behavior
Foundry discovery endpoints are public and return cached public-safe payloads. Marketplace product APIs may require a configured marketplace access path such as bearer token, RapidAPI proxy secret, GitHub entitlement, or Zapier automation key.
Caching and freshness
Responses are backed by generated or cached artifacts. They are meant for stable public discovery and integration, not direct access to internal systems or live provider dashboards.
Errors
Expect standard JSON error responses for missing products, invalid input, rejected access, or throttled requests. Public Foundry API traffic is rate limited to the configured public limiter.
Security notes
Examples use sanitized slugs and do not expose internal database IDs, private run IDs, owner-only endpoints, provider credentials, or bucket names.