Fact 156
Morgan Chen requested giving support this customer-safe sentence: “For current API authentication and webhook-related setup, please use our GraphQL API v2 quickstart here: https://docs.atlas-test.com/api/v2/graphql-quickstart; it reflects the current auth/header model we support now.”
Source evidence (1)
000873Nov 24, 2023 / 10:29 UTC-08:00
Rishi found one holiday-coverage docs issue: [Discord DM — Rishi Patel → Morgan Chen — Fri Nov 24, 2023 10:16 AM PT] Holiday-coverage wrinkle: the last stale refund-webhook cache result is still leaking through one old support macro. Stale macro text still in the support path "Refund webhook auth: send the customer the refund webhook quickstart for webhook verification. Internal lookup tag: refund webhook auth." API v1 result the macro is steering people toward - title: API v1 refund webhook quickstart - path: /api/v1/webhooks/refunds - snippet: "Use your v1 secret key to verify refund webhook requests and POST acknowledgements to /v1/webhooks/refunds." - same cached legacy result we still see under `refund webhook auth` Current API v2 support-path link to use instead https://docs.atlas-test.com/api/v2/graphql-quickstart Draft customer-safe sentence for coverage "For current API authentication and webhook-related setup, please use our GraphQL API v2 quickstart here: https://docs.atlas-test.com/api/v2/graphql-quickstart; it reflects the current auth/header model we support now." Please inspect the examples and DM Rishi in the current internal team chat. Narrow fix only: use the current API v2 support-path link for now, give support the customer-safe sentence, suppress or patch the stale macro on Monday, and do not reopen the API migration project.
Message 000873 in history