> ## Documentation Index > Fetch the complete documentation index at: https://proxy-docs.permify.co/llms.txt > Use this file to discover all available pages before exploring further. # List Tenants ## OpenAPI ````yaml post /v1/tenants/list openapi: 3.0.0 info: title: Permify API description: >- Permify is an open source authorization service for creating fine-grained and scalable authorization systems. version: v1.6.10 contact: name: API Support url: https://github.com/Permify/permify/issues email: hello@permify.co license: name: AGPL-3.0 license url: https://github.com/Permify/permify/blob/master/LICENSE servers: [] security: [] tags: - name: Permission - name: Watch - name: Schema - name: Data - name: Bundle - name: Tenancy paths: /v1/tenants/list: post: tags: - Tenancy summary: list tenants operationId: tenants.list requestBody: content: application/json: schema: $ref: '#/components/schemas/TenantListRequest' description: >- TenantListRequest is the message used for the request to list all tenants. required: true responses: '200': description: A successful response. content: application/json: schema: $ref: '#/components/schemas/TenantListResponse' default: description: An unexpected error response. content: application/json: schema: $ref: '#/components/schemas/Status' x-codeSamples: - label: go lang: go source: >- cr, err := client.Tenancy.List(context.Background(), &v1.TenantListRequest{ PageSize: 20, ContinuousToken: "", }) - label: node lang: javascript source: |- let res = client.tenancy.list({ pageSize: 20, continuousToken: "", }) - label: cURL lang: curl source: |- curl --location --request POST 'localhost:3476/v1/tenants/list' \ --header 'Content-Type: application/json' \ --data-raw '{ "page_size": 20, "continuous_token": "" }' components: schemas: TenantListRequest: type: object properties: page_size: type: integer format: int64 description: |- page_size is the number of tenants to be returned in the response. The value should be between 1 and 100. continuous_token: type: string description: |- continuous_token is an optional parameter used for pagination. It should be the value received in the previous response. description: >- TenantListRequest is the message used for the request to list all tenants. TenantListResponse: type: object properties: tenants: type: array items: $ref: '#/components/schemas/Tenant' description: tenants is a list of tenants. continuous_token: type: string description: >- continuous_token is a string that can be used to paginate and retrieve the next set of results. description: >- TenantListResponse is the message returned from the request to list all tenants. Status: type: object properties: code: type: integer format: int32 message: type: string details: type: array items: $ref: '#/components/schemas/Any' Tenant: type: object properties: id: type: string description: The ID of the tenant. name: type: string description: The name of the tenant. created_at: type: string format: date-time description: The time at which the tenant was created. description: >- Tenant represents a tenant with an id, a name, and a timestamp indicating when it was created. Any: type: object properties: '@type': type: string description: >- 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. additionalProperties: {} description: >- `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": , "lastName": } 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" } ````