Get Help

View as MarkdownOpen in Claude

Start With the Docs

For API and Platform questions, these docs are the first stop. Most integration failures are an auth header, a missing scope, a rate limit, or a parameter that is not in the spec.

1

Reproduce the Call

Reproduce against the Quickstart or the relevant API guide.

2

Match the HTTP Status

Match the HTTP status in API troubleshooting and the error code reference.

3

Confirm Authentication

Confirm authentication uses X-API-Key and YDC_API_KEY.

4

Contact With Logs

If the request still fails, contact us with the request ID, endpoint, timestamp, and response body from Platform Logs.

Contact Channels

The Platform itself is at you.com/platform. Product write-ups and announcements live on you.com/resources.

What We Support From These Channels

These channels cover the public APIs (Web Search, Answer, Contents, Research, Finance Research), authentication, keys, billing, rate limits, and Platform administration (members, SSO/SCIM enablement, Zero Data Retention).

The API references and guides are the integration contract. Support answers concrete request failures: auth, 4xx/5xx, unexpected payloads. Application architecture and from-scratch product builds stay with your team, except where an enterprise agreement includes that work. If a request fails, send the request ID and the response body rather than a general “it doesn’t work.”

Enterprise Support

Large enterprise customers with complex integrations get a dedicated account team and, when SSO or SCIM is in scope, a Customer Success Architect. That path is arranged in the agreement. Email [email protected] or your account team. We do not publish response-time SLAs on this page.

A CSA enables SSO and SCIM and Zero Data Retention. Custom QPS is set in the agreement. None of these is a self-serve Platform toggle.

FAQ

Read the docs page for the endpoint you are calling, then API troubleshooting. If you are still blocked, email [email protected] or ask in Discord. Include the endpoint, timestamp, status, and request ID.

The documentation is the integration guide for most customers. Enterprise accounts that need a more involved integration work with their account team. Reach us through the channels above for a concrete failure (auth, 4xx/5xx, unexpected payload), not for a from-scratch build of your product.