Integration guides / Zapier users and reviewers
ZentraFoundry Zapier API Documentation
Public API documentation for the ZentraFoundry Zapier automation integration.
Overview
ZentraFoundry provides automation-ready public-data signals and dataset diff workflows. This page documents the production API surface used by the ZentraFoundry Zapier integration.
Production API base
Use https://zentra.nimblique.studio as the production API base. The public documentation lives on zentrafoundry.com, while API requests are sent to the Zentra production API host.
- Homepage URL: https://zentrafoundry.com
- API documentation URL: https://zentrafoundry.com/docs/zapier
- OpenAPI JSON: https://zentrafoundry.com/docs/zapier/openapi.json
Authentication
The Zapier package sends the ZentraFoundry API key in the Authorization request header. Users do not enter an API base URL in Zapier; the production integration uses https://zentra.nimblique.studio. Use a placeholder in docs and examples: Authorization: Bearer <YOUR_ZENTRAFOUNDRY_API_KEY>. Customer API keys are issued during ZentraFoundry account activation or onboarding for the products and automations the customer is allowed to use.
- Header name: Authorization
- Header value format: Bearer <YOUR_ZENTRAFOUNDRY_API_KEY>
- Zapier auth field: ZentraFoundry API key
- No default key is published or shared between customers.
- The key is scoped to the public automation API surface documented here.
OpenAPI document
A static OpenAPI document is published for tooling and reviewer import. It contains only the six Zapier-visible automation operations and uses placeholder examples.
- https://zentrafoundry.com/docs/zapier/openapi.json
Endpoints
These are the six Zapier-visible operations. Trigger endpoints accept cursor and limit query parameters. Search actions accept query or q plus an optional limit. Run Dataset Diff accepts product_slug; when it is omitted, the production API applies the canonical Automation default procurement-automation-connector.
| Zapier key | Label | Method | Path |
|---|---|---|---|
| newMatchingTender | New Matching Tender | GET | /api/public/automation/triggers/new-tender-matches |
| newRecallAlert | New Recall Alert | GET | /api/public/automation/triggers/new-recall-alerts |
| datasetChanged | Dataset Changed | GET | /api/public/automation/triggers/dataset-changed |
| findTender | Find Tender | POST | /api/public/automation/actions/search-tenders |
| findRecall | Find Recall | POST | /api/public/automation/actions/search-recalls |
| runDatasetDiff | Run Dataset Diff | POST | /api/public/automation/actions/run-dataset-diff |
Search examples
Tender search can be tested with zapier-demo, ZAP-DEMO-TENDER-001, or government. Recall search can be tested with zapier-demo, ZAP-DEMO-RECALL-001, or product safety.
Response conventions
Zapier output uses stable string id fields, _dedupe_key values for polling, ISO-8601 timestamps with timezone, and empty arrays when no matching rows are available. Validation errors return JSON with a message field. Automation endpoints are protected by public marketplace throttling and account abuse controls.
Zapier usage notes
These endpoints are used by the ZentraFoundry Zapier integration for public-data triggers, searches, and dataset diff actions. Zapier review and listing status are separate marketplace processes; this documentation does not imply endorsement.
Support
For access questions, custom feeds, or integration help, use the public ZentraFoundry contact flow.
- https://zentrafoundry.com/contact