Contact PulsAPI
Four mailboxes, each read by the people who can actually answer. Pick the one that matches the question and you will skip a hop.
Where to write
hello@pulsapi.com
General questions, partnerships, and anything that does not fit below.
Within two business days.
support@pulsapi.com
Product problems, API questions, and account issues.
Within one business day. Business and Enterprise plans are prioritised; Enterprise has a named contact.
sales@pulsapi.com
Pricing, Enterprise plans, procurement, and security questionnaires.
Within one business day.
privacy@pulsapi.com
GDPR and CCPA requests, data deletion, and privacy questions.
Acknowledged within five days, and answered within 30 days, as GDPR and CCPA require.
Other routes
The support page has a form that opens a tracked ticket, plus answers to the questions that come in most often. Signed-in accounts can open tickets from Help & Support in settings, which attaches the account context automatically.
To ask PulsAPI to monitor a vendor it does not track yet, use Request a Service in the service directory rather than email — it captures the status-page URL, which is the one thing every such request needs.
For anything API-shaped — an endpoint that is missing from the specification, an MCP tool that does not do what you need — the developer hub lists what already exists, and support@pulsapi.com reaches the people who maintain it.
Product updates go out on X as @PulsApi.
Company details
PulsAPI Inc., founded October 2025, incorporated in Delaware, United States. The Terms of Service name Delaware as the governing law and forum; the privacy policy names PulsAPI Inc. as the data controller for GDPR purposes. More about the company is on the about page.
Need an answer faster than email?
Most product questions are already answered in the documentation, and the whole service catalog is public — no account needed to check whether a vendor is up.