Supaglue Rate Limits

Supaglue published no numeric rate limit for its own API — not on the API introduction page, not in any spec, and not in the archived docs anywhere. What it published is the exhaustion signal (HTTP 429, error code TOO_MANY_REQUESTS_ERROR, in the error table on the API introduction page) and, notably, an operation that reports the THIRD-PARTY provider's remaining quota rather than its own: GET /customers/{customer_id}/connections/{provider_name}/_rate_limit_info. That inversion is the finding — Supaglue treated the upstream SaaS limit as the limit that mattered, because a unified call is really a Salesforce or HubSpot call wearing a different URL. No X-RateLimit-* or RateLimit-* response headers and no Retry-After are documented, so a client cannot see how close it is to a wall until it hits one. The hosted service is now shut down (api.supaglue.io does not resolve); on a self-hosted deployment the throttle is whatever the deployer configures.