Encharge
Encharge is a behavior-based marketing automation platform built for SaaS companies, with a visual flow builder, broadcasts, segments, lead scoring, A/B testing, and 50+ native integrations (HubSpot, Stripe, Salesforce, Facebook Ads, and more). The platform combines email marketing automation, user profiles, and product-event tracking to send targeted emails based on what users do (or do not do) in a SaaS product. Encharge exposes REST, Ingest, and Transactional Email APIs authenticated with an API token.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Encharge the way a machine reads it — 16 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Encharge scores 30.9/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Encharge
Each block below is one kind of artifact we hold for Encharge. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Encharge REST API
REST API (v1) for managing people, segments, tags, fields, flows, broadcasts, and events in Encharge. Authentication is via an API key passed as the token query parameter or X-E...
Encharge Transactional Email API
REST API for sending transactional emails through Encharge. Accepts JSON payloads at POST /v1/emails/send and authenticates via the same API token used by the core REST API.
Encharge Ingest API
Ingest API for streaming people and activity events into Encharge from backend systems. Posts JSON payloads to ingest.encharge.io/v1/ using the same API token.
Encharge Account API
The Account API from Encharge — 1 operation(s) for account.
Encharge Events API
The Events API from Encharge — 2 operation(s) for events.
Encharge Fields API
The Fields API from Encharge — 2 operation(s) for fields.
Encharge Ingest API
The Ingest API from Encharge — 1 operation(s) for ingest.
Encharge People API
The People API from Encharge — 2 operation(s) for people.
Encharge Segments API
The Segments API from Encharge — 2 operation(s) for segments.
Encharge Tags API
The Tags API from Encharge — 1 operation(s) for tags.
Encharge Transactional Email API
The Transactional Email API from Encharge — 1 operation(s) for transactional email.
Scroll within the panel for all 11 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Encharge REST API
OPEN COLLECTIONSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Encharge — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/encharge · machine-readable index on apis.io