---
search:
  tags:
    - Device Types
    - POST
seo:
  description: >-
    Create a device type in the caller's org. Reference for the POST
    /v1/device-types/create endpoint in the Roboto REST API.
sidebar:
  label: Create device type
  badge: POST
title: Create device type
type: openapi-operation
---
Create a device type in the caller's org.

#### Access control
 - requires_org
 - Restricted tokens need the API scope `api.everything_else`

`POST /v1/device-types/create`

**Request body** (`application/json`, required)

- `name` (string, required)
- `description` (string | null)
- `metadata` (object)
- `tags` (string[])

Request body example:

```json
{
  "name": "string",
  "description": null,
  "metadata": {},
  "tags": [
    "string"
  ]
}
```

**Responses**

- `201` — CREATED
- `400` — Thrown when the conversation context (messages, system prompt, tool results) exceeds the model's context window limit. The token estimate and the model's context limit are not carried on the exception, so a caller cannot read usage numbers off it.
- `401` — Thrown when authentication fails
- `403` — Thrown if an operation would exceed a user or org level limit.
- `404` — Thrown if a user is attempting to perform an action unrecognized by the Roboto platform.
- `409` — Thrown if there is a conflict between a resource you're creating and another existing resource
- `410` — Thrown if a resource is missing or expired.
- `500` — An error the platform reported that this SDK release cannot resolve to a specific exception class. Reported for an element of a :py:class:\`\~roboto.http.BatchResponse\` whose error names a code this release defines no class for, or that arrived without a code, without a message, or as text that is not an error envelope at all. It carries whatever code and message the platform sent, so a caller handling the failure still learns what went wrong; when no message could be read, the message is the error's raw text. The error envelope carries no status code, so \`\`http\_status\_code\`\` reports the 500 inherited from :py:class:\`RobotoDomainException\` rather than the status the failure actually had.
- `501` — Thrown by shimmed out APIs which have not yet been implemented
- `503` — Thrown when a service is unavailable, such as when it's under heavy load and can't accept new requests. This is expected to be transient and ought to be retried.
- `504` — Thrown when the service times out while processing a request. This is exepcted to be transient and ought to be retried.
- `507` — Thrown when the server cannot complete the request because the response payload exceeds a storage or transport capacity limit (e.g., Lambda response size). This is NOT expected to be transient and should NOT be retried.

Response example, 201:

```json
{
  "data": {
    "device_type_id": "string",
    "org_id": "string",
    "name": "string",
    "description": null,
    "device_count": 0,
    "metadata": {},
    "tags": [
      "string"
    ],
    "created": "2019-08-24T14:15:22Z",
    "created_by": "string",
    "modified": "2019-08-24T14:15:22Z",
    "modified_by": "string"
  }
}
```