Confluent Partner API signup, organizations, and entitlements using a separately enrolled partner OAuth bearer token. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 8 of the suite's 489 admitted current operations. The enrolled confluent-partner connection supplies partner OAuth access token through connection-owned Bearer authentication and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.