Skip to main content
PATCH
/
api
/
v1
/
workspaces
/
{id}
Update workspace details
curl --request PATCH \
  --url https://api.luxxon.dev/api/v1/api/v1/workspaces/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "Acme Visuals",
  "availabilityState": "ONLINE",
  "coverageLat": 4.711,
  "coverageLng": -74.07,
  "coverageRadiusMeters": 500,
  "deviceKind": "PHONE"
}
'
{
  "statusCode": 200,
  "message": "Request successful",
  "data": {
    "id": "8c3a5b6f-1d2e-4f7a-9b8c-d1e2f3a4b5c6",
    "slug": "acme",
    "name": "Acme Visuals",
    "walletAddress": "0xAbC0000000000000000000000000000000000001",
    "roles": [
      "CONSUMER"
    ],
    "availabilityState": "OFFLINE",
    "coverageLat": 4.711,
    "coverageLng": -74.07,
    "coverageRadiusMeters": 500,
    "deviceKind": "PHONE",
    "lastSeenAt": null,
    "createdAt": "2026-05-13T11:30:00.000Z",
    "createdByWallet": "0xAbC0000000000000000000000000000000000001",
    "deletedAt": null
  },
  "timestamp": "2026-05-13T12:00:00.000Z"
}

Authorizations

Authorization
string
header
required

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

Path Parameters

id
string
required
Example:

"8c3a5b6f-1d2e-4f7a-9b8c-d1e2f3a4b5c6"

Body

application/json
name
string

Human-readable workspace name. 1–80 chars; trimmed server-side.

Example:

"Acme Visuals"

availabilityState
enum<string>

Supplier flips between ONLINE (dispatcher will pick) and OFFLINE (invisible). BUSY is API-owned and not settable here.

Available options:
ONLINE,
OFFLINE
Example:

"ONLINE"

coverageLat
number
Example:

4.711

coverageLng
number
Example:

-74.07

coverageRadiusMeters
number
Example:

500

deviceKind
enum<string>
Available options:
PHONE,
LAPTOP,
DRONE,
PTZ,
FIXED,
OTHER
Example:

"PHONE"

Response

Request successful

statusCode
number
required
Example:

200

message
string
required
Example:

"Request successful"

data
object
required

Endpoint-specific payload. See the per-endpoint schema.

timestamp
string
required
Example:

"2026-05-13T12:00:00.000Z"