C2 Cloud API

Responses

• 200 The authenticated user.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/me' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of audit records.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/activity-log' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Request body Required

Responses

• 200 Your profile, saved.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/me' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "Ayşe Yılmaz",
    "birthdate": "string",
    "identity_number": "string",
    "phone": "+90 532 000 00 00",
    "language": "tr-TR"
}'

Responses

• 200 Your settings.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/me/settings' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Request body Required

Responses

• 200 Your settings, saved.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/me/settings' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "enable_email_notifications": true,
    "enable_phone_notifications": true
}'

Responses

• 200 The billing information.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/account/billing-information' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Request body Required

Responses

• 200 The billing information, saved.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/account/billing-information' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "address": "string",
    "city": "string",
    "postal_code": "string",
    "country": "TR"
}'

Responses

• 200 The keys.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/ai/keys' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Request body Required

Responses

• 201 The key, with its secret — shown this once.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 409 At the key cap, another key is being created, or the login or account is barred. Nothing was created.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/ai/keys' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "ci runner"
}'

Parameters

Responses

• 200 The key, revoked.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/ai/keys/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Responses

• 200 The limits and the spend.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/ai/usage' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of virtual machines.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/instances' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The virtual machine.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/instances/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 200 The updated virtual machine.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/instances/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "string"
}'

Parameters

Responses

• 200 The machine's networks.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/instances/1/networks' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of live snapshots.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/instances/1/vm-snapshots' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 201 The snapshot, being taken.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/vm-snapshots' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "string"
}'

Parameters

Responses

• 204 Deleted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/instances/1/vm-snapshots/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The machine after the revert.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/vm-snapshots/1/actions/revert' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The schedules.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/instances/1/schedules' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 201 The schedule.
• 202 Created, not yet listed by the cloud.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/schedules' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "action": "start",
    "cron_expression": "0 8 * * 1-5",
    "timezone": "Europe/Istanbul"
}'

Parameters

Request body Required

Responses

• 200 The schedule.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/instances/1/schedules/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "cron_expression": "0 8 * * 1-5",
    "timezone": "Europe/Istanbul"
}'

Parameters

Responses

• 204 Deleted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/instances/1/schedules/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The notes.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/instances/1/annotations' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 201 The note.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/annotations' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "annotation": "string"
}'

Parameters

Responses

• 204 Deleted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/instances/1/annotations/annotation' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The events.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/instances/1/events' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The machine, as stored after the change.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/networks/1/actions/attach' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The machine, as stored after the change.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/networks/1/actions/detach' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The machine, as stored after the change.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/networks/1/actions/make-primary' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 200 The machine, as stored after the change.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/networks/1/actions/move' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "from_network_id": 1
}'

Parameters

Request body Required

Responses

• 200 The machine, as stored after the change.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/networks/1/actions/change-ip' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "ip_address": "10.1.1.20"
}'

Parameters

Responses

• 200 The virtual machine, started (or already running).
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/actions/start' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The virtual machine, stopped (or already stopped).
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/actions/stop' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The virtual machine, restarted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/actions/restart' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The virtual machine, after the password reset.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/actions/reset-password' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The virtual machine's password.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/instances/1/password' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A console session URL.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/instances/1/console' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 200 The virtual machine, with the ISO attached (or already attached).
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/actions/attach-iso' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "iso_id": 5
}'

Parameters

Responses

• 200 The virtual machine, with its ISO detached (or already detached).
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/instances/1/actions/detach-iso' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 200 The ISO.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/isos/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "string",
    "description": "string",
    "bootable": true
}'

Parameters

Responses

• 204 Deleted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/isos/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Request body Required

Responses

• 201 The open upload.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X POST 'https://cloud.core.gen.tr/api/v1/isos/uploads' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "string",
    "description": "string",
    "bootable": true,
    "filename": "string",
    "size": 1
}'

Parameters

Responses

• 200 The open upload.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/isos/uploads/upload' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 204 Aborted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/isos/uploads/upload' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The upload, with this part received.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X POST 'https://cloud.core.gen.tr/api/v1/isos/uploads/upload/chunks' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 201 The registered ISO.
• 202 Registered, not yet listed by the cloud.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/isos/uploads/upload/actions/complete' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of volumes.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/volumes' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The volume.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/volumes/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 200 The updated volume.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/volumes/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "string"
}'

Parameters

Request body Required

Responses

• 200 The volume, attached (or already attached to the named instance).
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/volumes/1/actions/attach' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "instance_id": 17
}'

Parameters

Responses

• 200 The volume, detached (or already detached).
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/volumes/1/actions/detach' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of the volume's snapshots, newest first.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/volumes/1/snapshots' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Optional

Responses

• 201 The snapshot, requested and being taken.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/volumes/1/snapshots' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "before-upgrade"
}'

Parameters

Responses

• 200 The snapshot.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/volumes/1/snapshots/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 204 Deleted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/volumes/1/snapshots/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 202 The restore started; the snapshot it started from.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/volumes/1/snapshots/1/actions/restore' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "restored-data"
}'

Parameters

Responses

• 200 The disk's retention schedules.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/volumes/1/snapshot-policies' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 201 The schedule.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/volumes/1/snapshot-policies' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "interval_type": "HOURLY",
    "max_snaps": 1
}'

Parameters

Responses

• 200 A page of ISOs.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/isos' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The ISO.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/isos/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of templates.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/templates' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The template.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/templates/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of compute offerings.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/compute-offerings' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of disk offerings.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/disk-offerings' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of ingress rules.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/ingress-rules' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Request body Required

Responses

• 201 The new ingress rule.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/ingress-rules' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "public_ip_address": "203.0.113.10",
    "protocol": "tcp",
    "public_port_start": 1,
    "public_port_end": 1,
    "private_port_start": 1,
    "private_port_end": 1,
    "instance_id": 17
}'

Parameters

Request body Required

Responses

• 200 The updated ingress rule.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/ingress-rules/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "private_port_start": 1,
    "private_port_end": 1,
    "instance_id": 17
}'

Parameters

Responses

• 204 The rule was deleted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/ingress-rules/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of egress rules.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/egress-rules' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Request body Required

Responses

• 201 The new egress rule.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/egress-rules' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "source_cidr": "10.0.0.0/24",
    "destination_cidr": "0.0.0.0/0",
    "protocol": "tcp",
    "port_start": 1,
    "port_end": 1
}'

Parameters

Responses

• 204 The rule was deleted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/egress-rules/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of networks.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/networks' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The network.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/networks/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 200 The network.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/networks/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "label": "string"
}'

Parameters

Responses

• 204 Released.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/networks/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of public IP addresses.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/public-ip-addresses' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The public IP address.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/public-ip-addresses/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 200 The updated public IP address.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/public-ip-addresses/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "reverse_record": "host.example.com"
}'

Parameters

Request body Required

Responses

• 200 The new address.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/public-ip-addresses/1/actions/move' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "network_id": 1
}'

Parameters

Responses

• 200 The plan.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/public-ip-addresses/1/move-plan' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of VPNs.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/vpn' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Request body Required

Responses

• 204 Switched.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/vpn' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "public_ip_address_id": 1,
    "enabled": true
}'

Parameters

Responses

• 200 A page of VPN users.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/vpn/users' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Request body Required

Responses

• 201 The new VPN user.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/vpn/users' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "username": "jdoe",
    "password": "string"
}'

Parameters

Responses

• 204 The VPN user was deleted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/vpn/users/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of affinity groups.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/affinity-groups' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Request body Required

Responses

• 201 The new affinity group.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/affinity-groups' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "web-tier",
    "affinity_type": "Host Affinity"
}'

Parameters

Request body Required

Responses

• 200 The updated affinity group.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/affinity-groups/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "instances": [
        17
    ]
}'

Parameters

Responses

• 204 The affinity group was deleted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/affinity-groups/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of DNS zones.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/dns-zones' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Request body Required

Responses

• 201 The new DNS zone.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/dns-zones' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "example.com"
}'

Parameters

Responses

• 200 The DNS zone.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/dns-zones/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 204 The zone (and its records) were deleted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/dns-zones/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of the zone's DNS records.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X GET 'https://cloud.core.gen.tr/api/v1/dns-zones/1/records' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Request body Required

Responses

• 201 The new DNS record.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/dns-zones/1/records' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "www",
    "type": "A",
    "data": "203.0.113.5"
}'

Parameters

Request body Required

Responses

• 200 The updated DNS record.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X PATCH 'https://cloud.core.gen.tr/api/v1/dns-zones/1/records/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "type": "A",
    "data": "203.0.113.6"
}'

Parameters

Responses

• 204 The record was deleted.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X DELETE 'https://cloud.core.gen.tr/api/v1/dns-zones/1/records/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of virtual machine products.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/virtual-machine-products' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The virtual machine product.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/virtual-machine-products/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of volume products.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/volume-products' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The volume product.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/volume-products/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of public IP address products.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/ip-address-products' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The public IP address product.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/ip-address-products/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of network products.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/network-products' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The network product.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/network-products/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of service products.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/service-products' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The service product.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/service-products/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of domain name products.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/domain-name-products' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The domain name product.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/domain-name-products/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 A page of subscriptions.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/subscriptions' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The subscription.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/subscriptions/1' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The subscription, terminated (or already terminated).
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.
• 502 The cloud's underlying IaaS control plane failed to carry out the request. The detail is a fixed, non-specific string in production — the provider's own error text routinely names internal hosts, pods and hypervisors. Treat this as retryable rather than as a client error.

curl -X POST 'https://cloud.core.gen.tr/api/v1/subscriptions/1/actions/cancel' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'

Parameters

Responses

• 200 The quote.
• 401 No token was presented, or it is invalid or expired.
• 403 Authenticated, but not permitted — the token lacks the required ability, a policy denied the action, the email address is unverified, or a support capability is insufficient.
• 404 No such resource, or it belongs to another customer. The two cases are deliberately indistinguishable.
• 409 The addressed resource has drifted from the upstream provider in a way this request cannot resolve. Refresh and retry.
• 422 The request body or query string failed validation.
• 429 Too many requests. Retry after the interval given in `Retry-After`.

curl -X GET 'https://cloud.core.gen.tr/api/v1/subscriptions/1/resize-quote' \
  -H 'Authorization: Bearer $C2_TOKEN' \
  -H 'Accept: application/json'