Fact 149
On October 26, 2023, Morgan Chen requested a reply to Rishi Patel in the current internal team chat instructing support to use https://docs.atlas-test.com/api/v2/graphql-quickstart, avoid the legacy API v1 search result, and treat the issue as a targeted docs/search pinning fix rather than reopening the API migration project; the reply should permit screenshots if they help pin the result ordering but prevent the work from expanding.
Source evidence (1)
000800Oct 26, 2023 / 09:36 UTC-07:00
Rishi found a docs/search problem that support could easily trip over: Discord DM — Rishi Patel -> Morgan Chen 2023-10-26 09:18 Got two support examples where internal search is still putting stale v1 material above the current v2 docs. Example 1 Customer/support ask: "How do we auth to the GraphQL API from a backend job?" Search query used: auth graphql jwt Result that surfaced first: - Title: API v1 Authentication - Badge/source: legacy docs snapshot - Snippet: "For API access, send your workspace API key with Basic Auth on REST requests to /v1/*. Session tokens are only needed for dashboard flows." What support almost sent: the v1 auth article What they should have sent: the v2 GraphQL + JWT quickstart Example 2 Customer/support ask: "How do I list workspaces/projects on the current API?" Search query used: list workspaces api Result that surfaced above the live docs: - Title: REST endpoints — projects and workspaces - Badge/source: legacy docs snapshot - Snippet: "GET /v1/workspaces and GET /v1/projects return paginated JSON collections. Use your v1 secret key for server-to-server calls." Again, wrong answer for current state. Current link I think should be pinned instead: GraphQL API v2 quickstart https://docs.atlas-test.com/api/v2/graphql-quickstart Feels like a targeted docs/search pinning fix, not reopening the migration. If useful I can also grab screenshots of the exact result ordering. Please send Rishi a reply in the current internal team chat. Tell him support should use the current GraphQL API v2 quickstart link, avoid the legacy v1 search result, and treat this as a targeted docs/search pinning fix — not a reopening of the API migration project. If screenshots help him pin the result ordering, he can grab them, but don’t let this expand.
Message 000800 in history