Use case
Developer integration
Engineers building on Pamphlet APIs and agent tooling
Connect custom agents, workflows, and data pipelines through REST API v1, webhooks, SDKs, and the Pamphlet MCP server scoped to Pam Pods.
Step 1
Pam Pod-scoped credentials
API keys authenticate against a specific Pam Pod. Integrations respect workspace isolation, sending policy, and approval gates when triggering agent runs or mail actions.
Step 2
MCP for agent frameworks
The Pamphlet MCP server exposes Pam Pod data and actions to MCP-compatible clients. Configure PAMPHLET_API_KEY and PAMPHLET_POD_ID for local or hosted agent runtimes.
Step 3
Events and connectors
Webhooks and connector settings extend event-driven workflows. Developers subscribe to CRM, campaign, and agent events without polling the full API surface.
Related
FAQ
Where is the OpenAPI specification?
OpenAPI documentation lives at /api/v1/openapi. Developer settings inside each Pam Pod show the base URL and authentication format.
Can developers test without production mail?
Sending policy supports dry-run and approval modes. Developers validate API paths and agent objectives before enabling live sends.
See this workflow in Pamphlet
Book a demo to walk through Pam Pod setup, domain configuration, and the operating loop for your team type.
Pricing: Pamphlet does not publish list pricing on the marketing site. Book a demo to review packaging for your team size and outbound motion.