Stensul

Stensul is an enterprise email and landing page creation platform — it calls the category "Governed Creation" — used by large marketing organizations to build, review, approve and deploy campaign assets without hand-coding HTML for every send. Marketers assemble emails and landing pages from brand-locked, developer-built modules; the platform runs the review and approval workflow, then pushes the finished asset into the ESP or marketing automation platform of record (Salesforce Marketing Cloud, Marketo, Adobe Campaign, Adobe Journey Optimizer, Oracle Eloqua, Braze, Iterable, Acoustic, Responsys, Epsilon PeopleCloud, Zeta and others). Stensul markets two enterprise APIs — a Content API for retrieving and distributing finished email content to any downstream system, and a User API for automating user provisioning and de-provisioning — both described as using OAuth server-to-server authentication with IP address allowlisting, with the User API additionally claiming support for SCIM provisioning standards. Neither API has a public reference, base URL, or machine-readable specification published on stensul.com; the endpoint pages are marketing descriptions that route to a sales conversation. The company was founded in 2015 and is headquartered in New York.

Stensul is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Email, Email Marketing, Marketing, and Marketing Automation.

Stensul’s developer surface includes documentation, support, engineering blog, pricing, authentication, and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

27.0/100 thin ▬ flat Agent 5/100 human only Front door AI 6/6 dominant Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessOpen

2 APIs

Company Email Email Marketing Marketing Marketing Automation Content Management Landing Pages Marketing Operations Enterprise Software Governance Collaboration Software-as-a-Service

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 27.0/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 4.9 / 17

Access Clarity 6.3 / 17

Operational Transparency 3.2 / 11

Contract Governance 1.9 / 10

Discoverability 5.5 / 9

Regulatory Posture 3.8 / 15

Agent readiness — 5/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/stensul/"><img src="https://apis.io/badge/stensul/card.svg" alt="Stensul on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

11 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 28.6 — up to +14.3 composite points
Access Clarity scores 36.8 — up to +12.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/stensul/apis.yml: open an issue on github.com/api-evangelist/stensul to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Adobe Exchange (publishers of Creative Cloud, Experience Cloud and Document Cloud integrations)	builds-on	17.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Stensul Content API

Enterprise API for retrieving finalized Stensul email content and distributing it to any platform in a customer's ecosystem, removing the manual export step between Stensul and ...

Stensul User API

Enterprise API for automating the provisioning, management and de-provisioning of Stensul users and their roles and permissions. Stensul's public integration page states it supp...

Stensul API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Stensul Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Stensul Rate Limits

0 limits

RATE LIMITS

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Stensul Authentication

0 schemes

SECURITY

Stensul Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Stensul Vulnerability Disclosure

Hackerone

SECURITY

Stensul Trust Center

SOC 2 Type 2

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Conventions

Conventions

Conformance

Conformance

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 4

Authentication, authorization, and security posture

TrustCenter

Compliance

Authentication

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Source (apis.yml)

aid: stensul
name: Stensul
description: Stensul is an enterprise email and landing page creation platform — it calls the category "Governed Creation"
  — used by large marketing organizations to build, review, approve and deploy campaign assets without hand-coding HTML for
  every send. Marketers assemble emails and landing pages from brand-locked, developer-built modules; the platform runs the
  review and approval workflow, then pushes the finished asset into the ESP or marketing automation platform of record (Salesforce
  Marketing Cloud, Marketo, Adobe Campaign, Adobe Journey Optimizer, Oracle Eloqua, Braze, Iterable, Acoustic, Responsys,
  Epsilon PeopleCloud, Zeta and others). Stensul markets two enterprise APIs — a Content API for retrieving and distributing
  finished email content to any downstream system, and a User API for automating user provisioning and de-provisioning — both
  described as using OAuth server-to-server authentication with IP address allowlisting, with the User API additionally claiming
  support for SCIM provisioning standards. Neither API has a public reference, base URL, or machine-readable specification
  published on stensul.com; the endpoint pages are marketing descriptions that route to a sales conversation. The company
  was founded in 2015 and is headquartered in New York.
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Open access
  confidence: medium
  probe_state: gated
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://stensul.com/wp-content/uploads/2025/10/Stensul-Logomark-Black-RGB.svg
url: https://raw.githubusercontent.com/api-evangelist/stensul/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-2026-08-29
specificationVersion: '0.20'
created: '2026-08-29'
modified: '2026-08-29'
tags:
- Company
- Email
- Email Marketing
- Marketing
- Marketing Automation
- Content Management
- Landing Pages
- Marketing Operations
- Enterprise Software
- Governance
- Collaboration
- Software-as-a-Service
tags_raw:
- Company
- Email
- Email Marketing
- Marketing
- Marketing Automation
- Content Management
- Landing Pages
- Marketing Operations
- Enterprise Software
- Governance
- Collaboration
- SaaS
apis:
- name: Stensul Content API
  description: Enterprise API for retrieving finalized Stensul email content and distributing it to any platform in a customer's
    ecosystem, removing the manual export step between Stensul and the downstream ESP/MAP. Stensul documents it publicly as
    using OAuth server-to-server authentication together with IP address allowlisting. No endpoint reference, base URL, or
    machine-readable contract is published on the public web; Stensul states a customer team builds and hosts the custom connection.
  humanURL: https://stensul.com/integrations/stensul-content-api/
  tags:
  - Content
  - Email
  - Integration
  properties:
  - type: Authentication
    url: authentication/stensul-authentication.yml
  - type: RateLimits
    url: rate-limits/stensul-rate-limits.yml
- name: Stensul User API
  description: Enterprise API for automating the provisioning, management and de-provisioning of Stensul users and their roles
    and permissions. Stensul's public integration page states it supports SCIM provisioning standards alongside OAuth server-to-server
    authentication and IP address allowlisting. The SCIM schema version, service provider configuration endpoint, and base
    URL are not published publicly, so the SCIM claim is recorded as a vendor assertion rather than a verified contract conformance.
  humanURL: https://stensul.com/integrations/stensul-user-api/
  tags:
  - Identity
  - User
  - Provisioning
  - SCIM
  tags_raw:
  - Identity
  - Users
  - Provisioning
  - SCIM
  properties:
  - type: Authentication
    url: authentication/stensul-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: TrustCenter
  url: security/stensul-trust-center.yml
- type: Website
  url: https://stensul.com/
- type: GitHubOrganization
  url: https://github.com/stensul
- type: Documentation
  url: https://helpdesk.stensul.com/en/
- type: Support
  url: https://helpdesk.stensul.com/en/
- type: Blog
  url: https://stensul.com/blog/
- type: BlogRSS
  url: https://stensul.com/feed/
- type: Pricing
  url: https://stensul.com/stensul-pricing-request/
- type: PrivacyPolicy
  url: https://stensul.com/privacy-policy/
- type: StatusPage
  url: https://status.stensul.com/
- type: Compliance
  url: https://stensul.com/security-trust-center/
- type: LLMsTxt
  url: llms/stensul-llms.txt
- type: Lifecycle
  url: lifecycle/stensul-lifecycle.yml
- type: Packages
  url: packages/stensul-packages.yml
- type: Authentication
  url: authentication/stensul-authentication.yml
- type: Conventions
  url: conventions/stensul-conventions.yml
- type: Conformance
  url: conformance/stensul-conformance.yml
- type: DomainSecurity
  url: security/stensul-domain-security.yml
- type: Plans
  url: plans/stensul-plans-pricing.yml
- type: RateLimits
  url: rate-limits/stensul-rate-limits.yml
x-enrichment:
  date: '2026-08-29'
  status: minimal
  artifacts_added: 15
  pass: local-v1
x-coverage:
  state: gated
  reason: sales-gate
  detail: 'Stensul markets two named enterprise APIs on https://stensul.com/our-integrations/api-endpoints/ — a Content API
    and a User API — but every route from those pages ends at "Request a demo": there is no developer portal, no api./docs./developer.
    subdomain (all three fail DNS resolution), no API reference in the public Intercom help center, which exposes exactly
    one collection ("Integrations"), and no base URL, endpoint, scope or error published anywhere a machine can read.'
  evidence:
  - url: https://stensul.com/our-integrations/api-endpoints/
    status: 200
  - url: https://stensul.com/integrations/stensul-content-api/
    status: 200
  - url: https://stensul.com/integrations/stensul-user-api/
    status: 200
  - url: https://docs.stensul.com/
    status: 0
  - url: https://developer.stensul.com/
    status: 0
  - url: https://api.stensul.com/
    status: 0
  - url: https://helpdesk.stensul.com/en/
    status: 200
  checked: '2026-08-29'

Stensul API — frequently asked questions

Does Stensul have an API?

Yes. APIs.io lists 2 APIs from Stensul, including Stensul Content API and Stensul User API.

How do I authenticate with the Stensul API?

Stensul uses bearer-token authentication (0 schemes). The details are profiled on APIs.io as Stensul Authentication.

Is the Stensul API ready for AI agents?

Stensul has a Kin Score of 27.0 out of 100 (thin) and an Agent Readiness score of 5.0 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/stensul"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/stensul/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/stensul/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.