Skip to main content
POST
/
cloud
/
v3
/
inference
/
applications
/
{project_id}
/
deployments
Create inference application deployment
curl --request POST \
  --url https://api.gcore.com/cloud/v3/inference/applications/{project_id}/deployments \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "application_name": "demo-app",
  "components_configuration": {
    "model": {
      "exposed": true,
      "flavor": "inference-16vcpu-232gib-1xh100-80gb",
      "scale": {
        "max": 1,
        "min": 1
      }
    }
  },
  "name": "my-app-deployment",
  "regions": [
    1,
    2
  ],
  "api_keys": [
    "key1",
    "key2"
  ]
}
'
{
  "tasks": [
    "d478ae29-dedc-4869-82f0-96104425f565"
  ]
}

Documentation Index

Fetch the complete documentation index at: https://gcore.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

API key for authentication. Make sure to include the word apikey, followed by a single space and then your token. Example: apikey 1234$abcdef

Path Parameters

​
project_id
integer
required

Project ID

Example:

1

Body

application/json
​
application_name
string
required

Identifier of the application from the catalog

Example:

"demo-app"

​
components_configuration
Components Configuration · object
required

Mapping of component names to their configuration (e.g., "model": {...})

Example:
{
  "model": {
    "exposed": true,
    "flavor": "inference-16vcpu-232gib-1xh100-80gb",
    "scale": { "max": 1, "min": 1 }
  }
}
​
name
string
required

Desired name for the new deployment

Maximum string length: 15
Example:

"my-app-deployment"

​
regions
integer[]
required

Geographical regions where the deployment should be created

Example:
[1, 2]
​
api_keys
string[]

List of API keys for the application

Example:
["key1", "key2"]

Response

200 - application/json

OK

​
tasks
string[]
required

List of task IDs representing asynchronous operations. Use these IDs to monitor operation progress:

  • GET /v1/tasks/{task_id} - Check individual task status and details Poll task status until completion (FINISHED/ERROR) before proceeding with dependent operations.
Example:
["d478ae29-dedc-4869-82f0-96104425f565"]