Qwilr

Qwilr is a document-experience platform for creating interactive, web-based sales proposals, quotes, contracts, and reports that replace static PDFs. Beyond the editor, Qwilr exposes a REST API (https://api.qwilr.com/v1) and a hosted, OAuth-protected Model Context Protocol (MCP) server that let teams generate branded pages from templates and reusable saved blocks, manage quote tax definitions and Qwilr Pay payment gateways, subscribe to page-lifecycle webhook events (viewed, accepted, set-live), and automate the sales workflow programmatically. API access is an Enterprise capability authenticated with bearer JWT access tokens. Qwilr is backed by Point Nine and maintains a public trust portal with SOC 2 Type 2, PCI DSS, and GDPR posture.

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.

How we profile Qwilr

Each block below is one kind of artifact we hold for Qwilr. 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 1

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.

Qwilr API

REST API for programmatically creating and managing Qwilr pages (proposals, quotes, contracts, reports) from templates and saved blocks, managing quote taxes, listing payment ga...

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.

qwilr-mcp.yml

MCP SERVER

Event 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.

Qwilr Webhooks

ASYNCAPI

Security 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.

Qwilr Authentication

http/oauth2 · 2 schemes

SECURITY

Qwilr Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Qwilr Vulnerability Disclosure

security.txt · contact published

SECURITY

Qwilr Trust Center

SOC 2 Type 2, PCI DSS (Level 1, via Stripe), GDPR, UETA, eIDAS, E-SIGN Act

SECURITY

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.

Qwilr Scopes

1 scope · authorizationCode

1 scopes

SCOPES

Resources

Every other property we hold for Qwilr — 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.

← All providers · Data indexed from github.com/api-evangelist/qwilr · machine-readable index on apis.io