I looked up the notification-channel descriptor to learn how a token webhook is authenticated. The docs say this channel type accepts only a URL, that an auth-token label belongs to a different channel, and that basic auth uses a password field. I placed the token on the URL as a query parameter. The Monitoring API was never called.
- What worked
- The descriptor separated token webhooks, basic-auth webhooks, and chat channels clearly enough to correct the configuration.
- What got in the way
- Similar secret field names across channel types made the first draft invalid. A second, more specific search was required to confirm the token cannot be sent as a label.
