---
title: "read attributes"
method: POST
path: "/v1/tenants/{tenant_id}/data/attributes/read"
tags: ["Data"]
---

# read attributes

`POST /v1/tenants/{tenant_id}/data/attributes/read`

## Path parameters

- `tenant_id` string, required

## Request body

- ReadAttributesBody — AttributeReadRequest defines the structure of a request for reading attributes. It includes the tenant_id, metadata, attribute filter, page size for pagination, and a continuous token for multi-page results.
  - `metadata` AttributeReadRequestMetadata — AttributeReadRequestMetadata defines the structure for the metadata of an attribute read request. It includes the snap_token associated with a particular state of the database.
    - `snap_token` string — The snap token to avoid stale cache, see more details on [Snap Tokens](../../operations/snap-tokens)
  - `filter` AttributeFilter — AttributeFilter is used to filter attributes based on the entity and attribute names.
    - `entity` EntityFilter — EntityFilter is used to filter entities based on the type and ids.
      - `type` string
      - `ids` string[]
    - `attributes` string[]
  - `page_size` integer — page_size specifies the number of results to return in a single page. If more results are available, a continuous_token is included in the response.
  - `continuous_token` string — continuous_token is used in case of paginated reads to get the next page of results.

## Response `200`

A successful response.

- AttributeReadResponse — AttributeReadResponse defines the structure of the response to an attribute read request. It includes the attributes retrieved and a continuous token for handling result pagination.
  - `attributes` Attribute[] — attributes is a list of the attributes retrieved in the read operation.
    - `entity` Entity — Entity represents an entity with a type and an identifier.
      - `type` string
      - `id` string
    - `attribute` string
    - `value` Any — `Any` contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message. Protobuf library provides support to pack/unpack Any values in the form of utility functions or additional generated methods of the Any type. Example 1: Pack and unpack a message in C++. Foo foo = ...; Any any; any.PackFrom(foo); ... if (any.UnpackTo(&foo)) { ... } Example 2: Pack and unpack a message in Java. Foo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class)) { foo = any.unpack(Foo.class); } // or ... if (any.isSameTypeAs(Foo.getDefaultInstance())) { foo = any.unpack(Foo.getDefaultInstance()); } Example 3: Pack and unpack a message in Python. foo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpack(foo) ... Example 4: Pack and unpack a message in Go foo := &pb.Foo{...} any, err := anypb.New(foo) if err != nil { ... } ... foo := &pb.Foo{} if err := any.UnmarshalTo(foo); err != nil { ... } The pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods only use the fully qualified type name after the last '/' in the type URL, for example "foo.bar.com/x/y.z" will yield type name "y.z". JSON ==== The JSON representation of an `Any` value uses the regular representation of the deserialized, embedded message, with an additional field `@type` which contains the type URL. Example: package google.profile; message Person { string first_name = 1; string last_name = 2; } { "@type": "type.googleapis.com/google.profile.Person", "firstName": <string>, "lastName": <string> } If the embedded message type is well-known and has a custom JSON representation, that representation will be embedded adding a field `value` which holds the custom JSON in addition to the `@type` field. Example (for message [google.protobuf.Duration][]): { "@type": "type.googleapis.com/google.protobuf.Duration", "value": "1.212s" }
      - `@type` string — A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in `path/google.protobuf.Duration`). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme `http`, `https`, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided, `https` is assumed. * An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one. Schemes other than `http`, `https` (or the empty scheme) might be used with implementation specific semantics.
  - `continuous_token` string — continuous_token is used in the case of paginated reads to retrieve the next page of results.

## Other responses

- `default` — An unexpected error response.

## Changes

- **2025-12-28** `f37e45046dd2` — 2 breaking
  - the `attributes/items/value/additionalProperties/` response's property type/format changed from `object`/`` to ``/`` for status `200`
  - the `details/items/additionalProperties/` response's property type/format changed from `object`/`` to ``/`` for status `default`
- **2024-08-23** `f3b10e35081b` — 1 breaking, 2 info
  - added required request body
  - added the media type `application/json` for the response with the status `200`
  - added the media type `application/json` for the response with the status `default`
- **2024-08-22** `282fb7ba2640` — 3 breaking
  - removed the request body
  - removed the media type `application/json` for the response with the status `200`
  - removed the media type `application/json` for the response with the status `default`
- **2024-03-19** `0bc305aa169f` — 2 breaking
  - the `attributes/items/value/additionalProperties/` response's property type/format changed from ``/`` to `object`/`` for status `200`
  - the `details/items/additionalProperties/` response's property type/format changed from ``/`` to `object`/`` for status `default`

[Change history](https://skmtc.dev/permify/apis/permify-api/changes/v1/tenants/:tenant_id/data/attributes/read/post.md)

---

[API](https://skmtc.dev/permify/apis/permify-api.md) · [All operations](https://skmtc.dev/permify/apis/permify-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/permify/permify-api/revisions/73b7d5b3742e/schema)