Create a registry credential
Saves a registry login for the org: basic takes username and password; aws_ecr takes accessKeyId, secretAccessKey and region; gcp_gcr takes serviceAccountKey. A missing credential field, or an unknown authType, returns 400. The credentials are stored encrypted, and the response is the credential's summary without them.
Required permission
Requires the registry.write permission. See Permissions for the roles and API key permissions that include it.
Command line
The orl CLI wraps this endpoint:
orl registry-credentials create --auth-type <auth-type> --credentials <credentials> --name <name> --server <server>apiKeyAuthorizationBearer <token>OpenRelay API key. Send it as Authorization: Bearer or_… (legacy vl_… keys still work).
orgId*stringapplication/json- body
name*stringserver*stringauthType*string"basic""aws_ecr""gcp_gcr"credentials*Created
application/json- response
id*stringname*stringserver*stringauthType*stringcreatedAt*stringcurl -X POST 'https://api.openrelay.inc/v1/orgs/string/registry-credentials/create' \ -H 'Content-Type: application/json' \ -d '{ "name": "string", "server": "string", "authType": "basic", "credentials": { "property1": "string", "property2": "string" }}'{ "id": "string", "name": "string", "server": "string", "authType": "string", "createdAt": "string"}List an org's registry credentials (no secrets) GET
Returns the org's container-registry credentials with id, name, server, auth type and creation time. Stored passwords and keys are never returned.
Delete a registry credential DELETE
Removes a registry credential from the org by id and returns 204 with no body. Deleting an id that does not exist also returns 204.