> For the complete documentation index, see [llms.txt](https://documentation.dnanexus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.dnanexus.com/developer/api/introduction-to-data-object-metadata/name.md).

# Name

Within a project, each object has a name, which is a UTF-8 string which must not match the regular expression `[\x00-\x1F]`. This means non-printable characters like whitespace tabs and newlines are not allowed. Object names do not need to be unique within the same project.

The name of an object is returned by the "describe" method, and modified by the "rename" method.

## API method: `/class-xxxx/rename`

### Specification

Renames an existing object in the specified project.

### Inputs

* `project` **string** (required) ID of the project or container containing the object to be modified.
* `name` **string** (required) The new name of the object.

### Outputs

* `id` **string** ID of the manipulated object.

### Errors

* `InvalidInput`
  * The input is not a hash.
  * `project` is missing or is not a string.
  * `name` is missing or is an empty string or matches the regular expression `[\x00-\x1F]`.
* `ResourceNotFound`
  * The specified object does not exist.
  * The specified project does not exist.
  * The specified project does not contain the specified object.
* `PermissionDenied`
  * If the object is open, UPLOAD access is required, otherwise CONTRIBUTE access is required for the specified project.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.dnanexus.com/developer/api/introduction-to-data-object-metadata/name.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
