canonical: https://jentic.com/apis/ecomatcher.com/ecomatcher # Ecomatcher Zapier API The EcoMatcher Zapier API authorizes and validates the credentials used to connect EcoMatcher to Zapier. Its published specification exposes a single operation that accepts an api_key header and confirms whether the credential is authorized, which workflows call before generating tree links to send trees in emails, gifts, or other automated actions. Authentication uses an api_key sent in a request header. ## For AI agents Authorize and validate EcoMatcher API credentials before a Zapier workflow runs. The published spec exposes a single credential-validation operation. ## Scope Does not expose tree-link generation, order placement, or reporting operations in its published spec. Use for authorizing and validating EcoMatcher Zapier credentials only. ## Capabilities - Authorize and validate your EcoMatcher API credentials before a workflow uses them - Confirm an api_key header is accepted so Zapier automations can run against EcoMatcher - Gate access to the EcoMatcher Zapier integration behind a credential check ## Use cases ### AI Agent Credential Check Before an agent triggers an EcoMatcher automation, it confirms the stored credential still works. The single authentication operation accepts the api_key header and reports whether the credential is authorized, so the agent can fail fast instead of starting a workflow that would be rejected. Through Jentic the agent discovers this operation by intent and calls it without a developer wiring the check by hand. Example prompt: Call the authentication operation with the api_key header to confirm the EcoMatcher credentials are valid before triggering a workflow ### Zapier Integration Setup When a user connects EcoMatcher to Zapier, the connection step verifies the key they entered. The authentication operation validates the api_key and surfaces an error immediately if it is rejected, so a misconfigured connection is caught during setup rather than at the first live run. This keeps a Zapier Zap from silently failing later. Example prompt: Validate the stored EcoMatcher api_key during Zapier connection setup and surface an error if it is rejected ### Pre-flight Validation in Automations Long-running automations check their credentials before doing work so an expired or revoked key does not break a chain mid-run. The authentication operation runs at the start of the automation and reports whether the credential is still authorized. An agent uses the result to halt the run cleanly instead of proceeding into failures. Example prompt: Run the authentication check at the start of an automation and halt the run if the credential is no longer authorized ## Key resources - **Authentication** — Authorize and validate EcoMatcher API credentials sent in the api_key header ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 0 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 72 / 100 - AI-Readiness & Agent Experience: 46 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 0 / 100 - **View full report:** https://jentic.com/apis/ecomatcher.com/ecomatcher/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the EcoMatcher Zapier API by hand means managing its api_key header and calling the credential-validation step before any automation runs. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The published spec exposes one operation, credential validation, which carries the api_key in a request header rather than the URL path. A rule bounds your agent to that single operation, so it can confirm credentials and has nothing destructive to call. - **Credential handling:** Your EcoMatcher api_key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'validate EcoMatcher credentials', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Zapier NLA API** — The Zapier automation platform this integration connects into - **Activepieces API** — Open-source workflow automation as an alternative to Zapier - **n8n API** — Self-hostable workflow automation with its own integration model - **Pipedream API** — Developer-focused integration and workflow platform ## FAQ ### What authentication does the EcoMatcher Zapier API use? The EcoMatcher Zapier API authenticates with an api_key sent in a request header per its OpenAPI spec, and its single published operation validates that credential. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context. ### What does the EcoMatcher Zapier API let me do? The published specification exposes one operation that authorizes and validates your EcoMatcher API credentials. Workflows call it to confirm the api_key is accepted before they generate tree links to send trees in emails or gifts. Operations for the tree-link generation itself are not part of this spec. ### What are the rate limits for the EcoMatcher Zapier API? The OpenAPI spec does not specify rate limits; see https://ecomatcher.com for current limits. The credential-validation operation is lightweight and is typically called once at the start of a workflow rather than repeatedly. ### Is there an EcoMatcher MCP server? You don't need an MCP server to give your agent the EcoMatcher Zapier API. Jentic connects it directly from the API Directory: import it, store your api_key once, and your agent calls the credential-validation operation. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context. ### Can I limit what my agent is allowed to do with the EcoMatcher Zapier API? Yes. The published spec exposes only the credential-validation operation, so a rule that allows that operation lets the agent confirm credentials and nothing else. The api_key travels in a request header, so rules bound which operation runs, and every call the agent makes is logged. ### How do I validate credentials with the EcoMatcher Zapier API through Jentic? Search Jentic for 'validate EcoMatcher API credentials' to find the authentication operation, pass the api_key, and read back whether it is authorized. To run it on your own infrastructure, install Jentic One from its GitHub repo.