Negatify
Log in

Contact

Let’s get you moving.

Choose the path that best matches your question. These resources can help you find integration guidance, get back to your workspace, or prepare the details needed to troubleshoot an issue.

Founder & CEO

Yuvraj Jaiswal

Negatify leadership and product enquiries.

Address

108/12, Patnipura,
Indore, Madhya Pradesh 452011,
India

How can we help?

Product and API questions

Browse the developer guide for endpoint details, authentication headers, request examples, and common errors before integrating a service.

Read the documentation

Account and project help

Sign in to access your projects, review credit usage, and manage your account through the Negatify workspace.

Open your account

Before you reach out

For a faster investigation, include the affected project, the steps that reproduce the issue, and any request ID or error message. Never include passwords or secret API credentials.

Review API errors

Help us resolve your request faster

Email us with a clear subject, a short description of what you were trying to do, the steps to reproduce the issue, and any non-sensitive error message or request ID. For billing questions, include the approximate date and project name. Never send passwords, access tokens, API keys, or payment-card details.

Email Negatify

Contact and support

Tell us what you are building and where you need help

For a useful first response, explain the outcome you expected, what happened instead, and which Negatify feature was involved. Include non-sensitive error details and the approximate time of the issue. Never email credentials, passwords, API keys, or payment-card information.

Product and technical support

For builder behavior, preview issues, project APIs, database operations, file uploads, AI chat, or email integration, include steps to reproduce the issue and the relevant endpoint or feature. You can link to the applicable Docs section in your message.

Billing and credit questions

For a purchase or usage question, include the plan/pack name, approximate purchase date, project name, and the service category shown in your dashboard. Do not send full card details or authentication secrets. The in-app billing history and usage display should be checked first.

Business enquiries

For partnerships, product feedback, or business conversations, share a short introduction, your organisation if relevant, the problem you are trying to solve, and a convenient way to follow up.

Privacy and security reports

If you believe a credential was exposed or a project boundary is behaving unexpectedly, avoid sharing exploit details publicly. Describe the impact and affected project at a high level, and rotate exposed credentials promptly.

Before sending your message

  • Use a subject that names the topic, such as “Billing question” or “Project storage integration”.
  • Describe the expected result and the actual result.
  • Include a minimal reproduction, timestamp, and non-sensitive error text where possible.
  • Remove personal customer data and all secrets from logs or screenshots.
  • For API questions, specify the endpoint and HTTP method without including authentication values.
Email Yuvraj Jaiswal