Paperless Post
Paperless Post is a New York City based digital and print stationery company whose platform lets people design, send, and manage online invitations, greeting cards, save-the-dates, and free Flyers for weddings, birthdays, holidays, business events, and other occasions. Founded in 2008 by siblings James and Alexa Hirschfeld, it pairs an in-house design studio with licensed designer collections (Oscar de la Renta, Rifle Paper Co., Marimekko and others) and adds RSVP tracking, guest messaging, event websites, mobile apps, and a Party Shop. Paperless Post publishes no public developer program, API reference, or machine-readable specification; the /api/v1 endpoints named in its robots.txt serve its own first-party web and mobile clients only.
Paperless Post publishes 1 API on the APIs.io network. Tagged areas include Company, Invitations, Events, Greeting Cards, and Stationery.
Paperless Post’s developer surface includes pricing, signup flow, support, engineering blog, authentication, and 17 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Paperless Post Party Shop Agent Commerce Surface
The Paperless Post Party Shop storefront is the only machine-callable surface on any paperlesspost.com host. It is Shopify-hosted and implements the Universal Commerce Protocol ...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
paperless-post-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type