Contact Y2 Intelligence

Get the right Y2 question to the right place

Email [email protected] for product, account, billing, API, documentation, privacy, or security questions. Include the page or endpoint involved, what you expected, what happened, and a request ID when an API response provides one. Never send an API key, password, payment-card number, authentication code, webhook signing secret, or sensitive customer content in an initial support message.

Product and account support

For sign-in, workspace, subscription, credit, report, project, or automation questions, include the account email and a concise description of the affected workflow. Screenshots can help when they exclude private evidence and credentials. Billing questions should include the invoice or checkout reference visible to you, but not complete payment details.

Developer and agent integrations

Before opening an integration question, review the developer hub, authentication and scope guide, and OpenAPI contract. For an API failure, include the HTTP method, path, response status, machine-readable error code, and request ID. For webhook problems, include the delivery event identifier and receiving status without copying the signing secret.

Privacy, safety, and source concerns

Use the same support address for privacy requests, suspected security issues, unsafe or inaccurate public content, and questions about cited source material. Put the category in the subject line and provide only the details needed to locate the issue. Privacy requests may require identity verification. Concerns about an original publisher's material may also need to be directed to that publisher.

Company address

This mailing address is published for company and legal correspondence. Email is the direct route for product support and technical diagnostics.