---
title: "Plans returns all plans."
method: GET
path: "/crescent/farming/v1beta1/plans"
tags: ["Query"]
---

# Plans returns all plans.

`GET /crescent/farming/v1beta1/plans`

## Request

- The document declares no server URL.
- Auth: none declared
- TypeScript: <https://skmtc.dev/crescent-network/apis/crescent-rest-and-grpc-gateway-docs/docs/crescent/farming/v1beta1/plans/get.ts> (a function with typed inputs; its response is checked against the schema)

Returns a list of all farming plans with pagination result.

## Query parameters

- `type` string
- `farming_pool_address` string
- `termination_address` string
- `staking_coin_denom` string
- `terminated` string
- `pagination.key` string, byte
- `pagination.offset` string, uint64
- `pagination.limit` string, uint64
- `pagination.count_total` boolean
- `pagination.reverse` boolean

## Response `200`

A successful response.

- object: QueryPlansResponse is the response type for the Query/Plans RPC method.
  - `plans` object[]
    - `type_url` 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. Schemes other than `http`, `https` (or the empty scheme) might be used with implementation specific semantics.
    - `value` string, byte: Must be a valid serialized protocol buffer of the above specified type.
  - `pagination` object: PageResponse is to be embedded in gRPC response messages where the corresponding request message has used PageRequest. message SomeResponse { repeated Bar results = 1; PageResponse page = 2; }
    - `next_key` string, byte
    - `total` string, uint64

## Other responses

- `400`: Bad Request
- `500`: Internal Server Error
- `default`: An unexpected error response

## Changes

- **2022-03-17** `050a36bde231`: 1 info
  - endpoint added
- **2022-01-24** `63a98ab49fe1`: 1 breaking
  - api path removed without deprecation
- **2022-01-24** `9df0a4d8de8e`: 1 info
  - endpoint added
- **2022-01-24** `c74d7f3d449c`: 1 breaking
  - api path removed without deprecation
- **2022-01-14** `0a864cc5519e`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/crescent-network/apis/crescent-rest-and-grpc-gateway-docs/changes/crescent/farming/v1beta1/plans/get.md)

---

[API](https://skmtc.dev/crescent-network/apis/crescent-rest-and-grpc-gateway-docs.md) - [All operations](https://skmtc.dev/crescent-network/apis/crescent-rest-and-grpc-gateway-docs/llms.txt) - [OpenAPI document](https://skmtc.dev/crescent-network/apis/crescent-rest-and-grpc-gateway-docs/revisions/ddf5133cea9d?raw)