Skip to main content
GET
/
storage
/
notifications
/
v1
/
events
/
configurator
Get possible list of events
curl --request GET \
  --url https://api.gcore.com/storage/notifications/v1/events/configurator \
  --header 'Authorization: <api-key>'
{
  "example": {
    "reaching_files_quantity": [
      {
        "bucket_name": "<string>",
        "count": 123,
        "storage_name": "<string>",
        "uuid": "<string>"
      }
    ],
    "reaching_used_requests": [
      {
        "bucket_name": "<string>",
        "count": 123,
        "storage_name": "<string>",
        "uuid": "<string>"
      }
    ],
    "reaching_used_space": [
      {
        "bucket_name": "<string>",
        "bytes": 123,
        "storage_name": "<string>",
        "uuid": "<string>"
      }
    ],
    "reaching_used_traffic": [
      {
        "bucket_name": "<string>",
        "bytes": 123,
        "storage_name": "<string>",
        "uuid": "<string>"
      }
    ]
  },
  "structure": [
    {
      "fields": [
        {
          "name": "storage_name",
          "type": "number, bool, text"
        }
      ],
      "name": "reaching_files_quantity"
    }
  ]
}

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

Response

EventsMetaResponse

EventsMeta describe how to form POST/PATCH request

​
example
object

Events for storage notification

​
structure
object[]

Structure of request body