- General & support — contact@myappapi.com. For questions about the documentation, integration help, or anything that doesn't fit one of the categories below.
- Content corrections — corrections@myappapi.com. If you've spotted an error in a guide, a stale code sample, or a broken link, this is the fastest path to getting it fixed. Please include the page URL.
- Security disclosures — security@myappapi.com. For responsible disclosure of vulnerabilities. Please give us a reasonable window to investigate before public disclosure.
- Partnerships and press — contact@myappapi.com with the subject prefixed
[Partnership]or[Press].
Response times
We aim to acknowledge substantive emails within a few business days. Requests that need a code change or a page rewrite take longer; we'll always acknowledge first and follow up when the work is done.
Community channels
For questions that other developers can answer faster than we can, the public channels are usually the better starting point:
- Community page — overview of where conversation happens.
- GitHub — issues and pull requests against the open-source SDK repositories.
What not to send by email
Please don't send credentials, API keys, or anything that looks like personal data belonging to your end users. If a bug report needs that material, contact us first and we'll arrange a secure handoff. For privacy-related requests covered under GDPR or CCPA, see the privacy policy for the dedicated process.
Mailing address
We don't list a postal address publicly. For contractual matters that genuinely require one, email contact@myappapi.com and we'll provide the appropriate address based on the request.