Knak
Knak is a no-code email and landing page creation platform built for enterprise marketing teams. Marketers design on-brand, responsive emails and landing pages in a drag-and-drop builder, then sync the finished HTML directly into their marketing automation platform (Marketo, Eloqua, Salesforce Marketing Cloud, Braze, HubSpot and others) without writing code or waiting on developers. For technical teams Knak publishes a documented developer surface -- the Knak Enterprise REST API for automating users, assets, themes, modules, brands, folders, merge tags and translation requests; the Knak Send Contacts API; a SCIM 2.0 API for identity-provider driven user provisioning; signed webhooks for asset and translation lifecycle events; a set of customer-implemented integration contracts (Custom DAM, Custom Validator, Custom Sync Location); and a hosted, OAuth 2.1 protected MCP server that lets AI clients generate and browse Knak assets.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Knak the way a machine reads it — 28 machine-readable artifacts across 21 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 — Knak scores 55.4/100 (developing), with a separate agent-readiness read of 61/100 (agent native). 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 Knak
Each block below is one kind of artifact we hold for Knak. 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 21
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.
Knak Asset Custom Fieldsets API
The Asset Custom Fieldsets API from Knak — 2 operation(s) for asset custom fieldsets.
Knak AssetFolders API
The AssetFolders API from Knak — 2 operation(s) for assetfolders.
Knak Assets API
The Assets API from Knak — 7 operation(s) for assets.
Knak AvailablePlatforms API
The AvailablePlatforms API from Knak — 1 operation(s) for availableplatforms.
Knak Brands API
The Brands API from Knak — 1 operation(s) for brands.
Knak Contacts API
Create, retrieve and list contacts in Knak Send.
Knak DAM Assets API
Endpoints to retrieve DAM Assets
Knak Fields API
Create and list custom contact fields (schema metadata).
Knak Integrations API
The Integrations API from Knak — 1 operation(s) for integrations.
Knak MarketingPlatformSyncs API
The MarketingPlatformSyncs API from Knak — 1 operation(s) for marketingplatformsyncs.
Knak MergeTags API
The MergeTags API from Knak — 2 operation(s) for mergetags.
Knak Modules API
The Modules API from Knak — 3 operation(s) for modules.
Knak OAuth2 API
Endpoints that need to be implemented to support OAuth2
Knak Project Management API
The Project Management API from Knak — 1 operation(s) for project management.
Knak Status API
The Status API from Knak — 1 operation(s) for status.
Knak Sync Location API
Endpoints to retrieve Sync Location
Knak SyncStatuses API
The SyncStatuses API from Knak — 1 operation(s) for syncstatuses.
Knak Themes API
The Themes API from Knak — 2 operation(s) for themes.
Knak TranslationRequests API
The TranslationRequests API from Knak — 5 operation(s) for translationrequests.
Knak Users API
The Users API from Knak — 4 operation(s) for users.
Knak Validation API
The Validation API from Knak — 1 operation(s) for validation.
Scroll within the panel for all 21 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
knak-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Knak Enterprise Webhooks
ASYNCAPISecurity Posture 4
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Knak — 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 3
Portal, sign-up, and the first successful call
Documentation 5
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/knak · machine-readable index on apis.io