Authorization header.
POST /resources
Create a new resource in your workspace. Supply a name and type at minimum; attach arbitrary key-value metadata to keep your resources organized.
A human-readable label for the resource. Must be between 1 and 255 characters.
The resource type. Accepted values are
standard, premium, and custom. This field cannot be changed after creation.An optional key-value object for storing additional context, such as environment tags or internal identifiers. All keys and values must be strings.
201 Created
JSON
The newly created resource object.
GET /resources
List all resources in your workspace. Filter by status or type and paginate through results using limit and offset.
The maximum number of resources to return. Accepted range is
1–100.The number of resources to skip before returning results.
Filter resources by lifecycle status. Pass
active to return only active resources, or archived to return only archived ones. Omit to return all.Filter resources by type. Accepted values are
standard, premium, and custom.200 OK
JSON
GET /resources/{id}
Retrieve a single resource by its ID. Replace {id} in the path with the resource’s res_ prefixed identifier.
200 OK
JSON
The API returns a
404 Not Found error if the resource ID does not exist in your workspace or belongs to a different workspace.PUT /resources/{id}
Update an existing resource’s name or metadata. Pass only the fields you want to change — omitted fields retain their current values.
A new display name for the resource.
A replacement metadata object. This fully overwrites the existing metadata; perform a read-modify-write if you need to preserve existing keys.
200 OK
The response returns the full updated resource object with the same shape as GET /resources/{id}.
DELETE /resources/{id}
Permanently delete a resource by its ID. A successful request returns 204 No Content with an empty body.
204 No Content
The response body is empty on success.