Mockfly
Contact

Contact Mockfly

One inbox, read by the people who build Mockfly. No chatbot, no ticket robot, no phone tree.

Email us at[email protected]Support, bugs, feature requests and billing — all the same address.

What to expect

We answer in English or Spanish, normally within one business day, Monday to Friday. Professional and Company plans get priority. If your message is about an endpoint that stopped responding, check status.mockfly.dev first — if there is an incident it is already posted there, and you'll get an answer faster from the status page than from us.

A lot of what reaches this inbox is already answered on the FAQ and in the documentation. Worth thirty seconds before you write, but if you'd rather just ask, ask.

Reporting a bug

Email [email protected] and include whatever you have of the following. It's the difference between a fix today and three emails of back and forth:

  • The project namespace and the endpoint path and HTTP method.
  • What you expected the endpoint to return, and what it actually returned.
  • Roughly when it happened, so we can line it up with your request logs.
  • Whether it was the web app, a call to your mock URL, the Chrome extension or mockfly-cli — and the CLI version if that's where it broke.

Requesting a feature

Same address, and it genuinely gets read by the developers rather than filed. Tell us what you were trying to do and where Mockfly got in the way, not just the feature you have in mind — the problem is usually more useful to us than the proposed solution. You can also ping @getmockfly if it fits in a tweet.

Plans, invoices and teams

Billing questions, invoices, VAT details, extra seats, centralised billing, volume discounts and custom integrations all go to the same inbox — say which plan you're on and we'll take it from there. What each plan includes is on pricing, and what Mockfly looks like for a whole team is on Mockfly for teams.

Privacy and your data

To access, correct, export or delete the personal data we hold about you, write to [email protected] and we'll handle it. What we store and why is set out in the privacy policy.

All the channels, in one place