Skip to main content
POST
/
api-keys
Create an organization API key
curl --request POST \
  --url https://api.staging-2tid4c.ezyshield.com.au/management/v1/api-keys \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "<string>",
  "abilities": [
    "organization_api_key:read"
  ]
}
'
{
  "data": {
    "id": "<string>",
    "name": "<string>",
    "abilities": [
      "<string>"
    ],
    "creator": {
      "id": "<string>",
      "name": "<string>",
      "email": "<string>",
      "created_at": "2023-11-07T05:31:56Z",
      "updated_at": "2023-11-07T05:31:56Z"
    },
    "created_at": "2023-11-07T05:31:56Z",
    "last_used_at": "2023-11-07T05:31:56Z",
    "expires_at": "2023-11-07T05:31:56Z",
    "token": "<string>"
  }
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
​
name
string
required

The name of the API key.

Maximum string length: 255
​
abilities
enum<string>[]
required

The abilities/permissions for the API key.

Available options:
organization_api_key:read,
organization_api_key:write,
entity:read,
entity:write,
entity_api_key:read,
entity_api_key:write

Response

ApiKeyResource

​
data
ApiKeyResource · object
required