Check that the key is a Cloud API key with the Cloud resource management scope rather than a key for a specific Kafka cluster, and that the account that owns the key has the OrganizationAdmin role.
Confluent
Connect your Confluent Cloud organization to Ploy to automatically discover user accounts, pending invitations, service accounts, and the roles each of them holds. This keeps your Confluent access picture up to date in Ploy.
Before you begin
You need access to the Confluent Cloud console as a user with the OrganizationAdmin role, so the API key can read all users, service accounts and role bindings in your organization.
Ploy needs a Cloud API key (an organization-level key for the Confluent Cloud management APIs). Keys scoped to a specific Kafka cluster, Schema Registry or Flink will not work.
Create a Cloud API key in Confluent Cloud
Log in to the Confluent Cloud console as a user with the OrganizationAdmin role.
Open the menu in the top-right corner and click API keys.
Click Add API key.
For the owner, select My account (simplest), or a service account that has the OrganizationAdmin role.
For the scope, choose Cloud resource management — the organization-wide scope for management APIs. Do not pick a specific Kafka cluster or other resource.
Give the key a name such as "Ploy", then create it.
Copy the Key (the key ID) and the Secret. Confluent shows the secret only once, so keep it to hand until you have finished the next section.
Connect Confluent to Ploy
In Ploy, click Integrations in the left sidebar.
Click Add new integration and search for Confluent.
In Confluent Cloud API Key ID, paste the key ID (for example
ABCDE12345FGHIJ).In Confluent Cloud API Key Secret, paste the secret.
Save the connection. Ploy verifies the credentials by looking up your Confluent organization, and the connection is labelled with your organization's name.
What data syncs
Users: every user in your Confluent Cloud organization, with name, email and login type.
Invitations: pending invitations, so access is visible from the moment someone is invited.
Service accounts: the non-human identities used by your applications and pipelines.
Role bindings: which Confluent roles each user and service account holds across the organization.
Data syncs periodically to keep Ploy up to date.
Troubleshooting
"Could not connect to Confluent with these credentials"
Lost the secret
Confluent only displays an API key's secret once. If you no longer have it, create a new API key and connect again in Ploy.