> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cocoondata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# <access-service>/api/v1/items/status

## URL structure&#x20;

```text theme={null}
https://access-service.xy-company.com/api/v1/items/status
```

## Supported methods and overview&#x20;

* `POST` - used to retrieve information about the current status of one or more [Secure Objects](/2.16/api/creating-secure-objects-and-collections.md#secure-object) (i.e. *Incomplete*, *Created* or *Deleted*) as well as one or more [collections](/2.16/api/creating-secure-objects-and-collections.md#collection).

## Detailed description&#x20;

This API endpoint retrieves information about the current status of one or more Secure Objects (i.e. *Incomplete*, *Created* or *Deleted*) as well as one or more collections, based on their IDs.

Collections can have one of two statuses - *Created* or *Deleted*. However, *Deleted* collections are not returned in responses from requests to this endpoint.

Also returned in responses are details about the Covata user who owns each item returned in the response.

## Supported roles&#x20;

This API endpoint supports the following Covata user [roles](/2.16/admin/administering-users.md#a-users-roles) (as described in the [Covata Platform Administrator's Guide](/2.16/admin.md)):

* [Originator](/2.16/admin/administering-users.md#originator-role)
* [Collaborator](/2.16/admin/administering-users.md#collaborator-role)

The Covata Platform's resources available to one of these Covata users (above) is determined by the access token passed in the [header](/2.16/api/access-service-api-v1-items-status.md#access-service-api-v1-items-status-required-headers) of requests to this endpoint.

## Required headers&#x20;

* `Authorization: Bearer a1b2c3d4-e5f6-g7h8-i9j0-k1l2m3n4o5p6` \

  where the `Bearer` token is the appropriate access token.
* `Content-Type: application/json`

## Optional parameters&#x20;

The following optional parameter can be sent in the body of the POST request, as an individual member of a JSON object:

* **ids** - An array of one or more [item](/2.16/api/creating-secure-objects-and-collections.md#item) IDs (i.e. of [Secure Objects](/2.16/api/creating-secure-objects-and-collections.md#secure-object) and/or [collections](/2.16/api/creating-secure-objects-and-collections.md#collection)).

  **Example ():**

Although omitting the **ids** parameter above in a request serves no purpose, an empty JSON object must at least be passed in the body of POST requests to this endpoint for a successful response:

* `{}`

## Returns&#x20;

A JSON-formatted response containing the following members:

* **count** - .
* **offset** - .
* **items** - .

  * **id** - .
  * **owner** - .

    * **email** - .
    * **firstName** - .
    * **lastName** - .
    * **id** - .
  * **state** - .

  **Example (response from ...):**


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.