# 400 Bad Request When Using a Ring ID

This article examines an error that might occur when you create an issue using YouTrack REST API. You can face this error when the request body contains a Ring ID instead of a YouTrack entity ID.

## Error Message

```JSON
{
    "error": "bad_request",
    "error_description": "Invalid structure of entity id: 039de813-e6e5-4b14-9d55-1361df908adf"
}
```

## Request Details

Here are the details about a sample request that might result in this error.

| Attribute | Value |
| --- | --- |
| Request method | POST |
| Endpoint | `/api/issues` |
| Request body |     ```JSON {     "project": {         "id": "039de813-e6e5-4b14-9d55-1361df908adf"     },     "summary": "yttool test summary",     "description": "yttool test description" } ```    |
| HTTP response code | 400 |

## Troubleshooting

Here are some possible causes and suggestions on how to overcome this error and create the issue.

### Cause

The value in the `project.id` attribute is a Ring ID. The `/api/issues` endpoint expects the YouTrack entity ID of the project.

### Solution

Replace the Ring ID with the YouTrack entity ID of the target project.

To find the project ID, send a GET request to the list of projects and request the `id` field:

```
/api/admin/projects?fields=id,shortName,name
```

Then use the project ID from the response body in the issue creation request.