Coolify logoCoolify
Cloud

Log out from a registry on a server

API server

https://app.coolify.io/api/v1

Choose where to send API requests

This changes the request URL and code examples on every endpoint page.

API server type

Requests will use

https://app.coolify.io/api/v1

Use only a Coolify URL you trust. Sending a test request also sends the API token you enter.

DELETE
/servers/{uuid}/registries/{registry}

Run docker logout on the server for a registry. Needs a token with the write and deploy permissions.

Authorization

bearerAuth
AuthorizationBearer <token>

Go to Keys & Tokens / API tokens and create a new token. Use the token as the bearer token.

In: header

Path Parameters

uuid*string

Server UUID

registry*string

Registry host, optionally with a port, for example registry.example.com:5000.

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://app.coolify.io/api/v1/servers/string/registries/string"
{  "message": "Logged out from ghcr.io."}
{  "message": "Invalid token."}
{  "message": "Unauthenticated."}
{  "message": "Resource not found."}
{  "message": "Validation error.",  "errors": {    "name": [      "The name field is required."    ],    "api_url": [      "The api url field is required.",      "The api url format is invalid."    ]  }}

Log in to a registry on a server POST

Run docker login on the server, writing to the Docker config that deployments use. Logging in again to the same registry replaces the saved login. Needs a token with the write and deploy permissions.

Migrate server to another Coolify instance POST

Start a transfer in the background: export this server, import and claim it on the target instance (with the given token), then disable automations here. All secrets of the server, also locked environment variables, are sent to the target. Follow the progress with GET /servers/{uuid}/transfer. The target URL must use https. Requires read:sensitive and write, and the owner role of the server team.