--- title: "Get Latest Agreements" method: GET path: "/agreements" tags: ["Documents"] --- # Get Latest Agreements `GET /agreements` When opening an account, the user has to agree to accept certain types of contractual documents, like privacy policy or terms and conditions. ## Query parameters - `cursor` string - `limit` integer ## Headers - `LMG-Data-Privacy-Access-Principal` string, required - `LMG-Data-Privacy-Access-Justification` string, required ## Response `200` Successful Response - EncodedPaginatedCollectionResponseAgreementResponse - `data` AgreementResponse[], required — The elements of the response. - `id` string, required — The identifier for this document. This will be later used as a value for the property `agreements[].agreement_id` for account creation. - `type` 'pricing_table' | 'privacy_policy' | 'terms_and_conditions', required — This property describes the underlying type of a document. In a list, you can use this value to select a different icon for eahc category or make sure, you always present those documents in a fixed order irrespective of the actual translation of the document title. - `url` string, url, required — A reference to the actual document. You can use this URL to present the document to the user. It can be accessed without special headers like `Authorization` or the `LMG-Data-Privacy-*` ones, so you have full flexibility for presentation and you can choose among:
  1. Showing the document using an In-App Browser.
  2. Showing the document using an external Browser App.
  3. Provide the user with your own options to download or forward the document.
- `language` string, required — The (natural) language for the document. This will can either be a pure language code like `"de"` or `"pl"` or a regional language code like `"en_GB"` or `"de_CH"`. When determining which one to prefer for display, we recommend to implement one of following strategies:
  1. If you have a list of preferred languages for the user, such as iOS's Locale.preferredLanguages, iterate that list until you find the first language that has a document provided.
  2. If you don't have a list of preferred languages, try to detect the regional language preference from the environment (e.g. "de_AT"). If there is a document for that one, present it to the user. If not, try presenting one for the language-part only (in case of "de_AT", that would be "de").
In either case, if there is no match with these lists, we recommend you pick a value that will match your application's default. A German version ("de") will always be provided. - `name` string, required — The localized name of the document. Use this value to reference to that document in the user interface. - `pagination` Pagination, required — Information about accessing elements beyond the ones that were returned. - `next_cursor` string — When fetching long lists of elements, you can use our pagination feature to fetch batches of data. If a response contains the property `pagination.next_cursor`, you can pass its value via the query item `cursor` to generate the request for the next batch of data. ## Other responses - `400` — Bad Request - `401` — Unauthorized - `404` — Not Found - `422` — Unprocessable Entity - `5XX` — Server Error --- [API](https://skmtc.net/lemon/apis/lemon-markets-brokerage-api.md) · [All operations](https://skmtc.net/lemon/apis/lemon-markets-brokerage-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lemon/lemon-markets-brokerage-api/versions/3c8cfd3a96c9/schema)