Groupon Authentication
Groupon publishes no anonymously-readable OpenAPI, so this profile is derived from what the live gateway itself says. Every path on api.groupon.com — the root, /v2/*, /graphql, /mcp, /.well-known/* — returns the identical response {"error":{"httpCode":401,"message":"'client_id' is invalid"}}. The gateway therefore names its own credential: a client_id. No WWW-Authenticate header is returned, no OAuth or OpenID discovery document is served on any Groupon host, and no bearer-token challenge is issued, so this is a plain API-key scheme, not OAuth. Nothing about scopes, key issuance or rotation could be read: the developer portal that would document it (www.groupon.com/developers) is behind a Cloudflare managed bot challenge that returns 403 to every automated client, including the Internet Archive.
Groupon declares 2 security scheme(s) across its OpenAPI definitions.
Security Schemes
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.