> ## Documentation Index > Fetch the complete documentation index at: https://docs.grainfinance.co/llms.txt > Use this file to discover all available pages before exploring further. # Rates > Retrieves offline hedge quote proposals for selected currency pairs. Partners can use these pre-fetched proposals - avoiding the need for a real-time quote per transaction. ## OpenAPI ````yaml GET /offline-rates openapi: 3.1.0 info: title: Grain API version: 1.0.0 description: >- Grain's API provides a comprehensive set of endpoints for managing hedging, spot transactions, pricing, and fund movements - enabling seamless integration of FX workflows into your platform. Each API call follows REST conventions, uses secure authentication, and returns standardized responses for consistency across environments. license: name: Creative Commons Attribution 3.0 contact: name: Grain Finance url: https://docs.grainfinance.co email: support@grainfinance.co termsOfService: https://grainfinance.co/terms-of-service/ x-apiClientRegistration: url: https://grainfinance.co/partners servers: - url: https://api.grainfinance.co/v1 description: Grain API security: [] tags: - name: Hedges description: >- Hedge objects represent transactions that lock exchange rates for future dates. A single hedge locks an exchange rate for a future transaction between two currencies. - name: Dual Hedges description: >- A dual hedge mitigates FX risk by automatically generating two linked hedge legs - a customer leg and a supplier leg - both routed through the customer's functional currency. This structure reduces exposure to currency fluctuations for both cash flow and accounting purposes, while allowing independent tracking and reporting of each hedge leg. - name: Customers description: >- Customer objects represent your end customers on the Grain platform. A customer must be created before a hedge or spot transaction can be initiated. - name: Pricing description: >- Pricing endpoints provide access to FX rates for currency pairs that are not being hedged. These endpoints can be used for live rate display or bulk retrieval to support high-volume quoting workflows. - name: Spots description: >- Spot objects represent currency conversions executed for immediate or near-term settlement. - name: Conversions description: >- Conversion objects represent currency conversions executed for immediate or near-term settlement. - name: Wallets description: Endpoints to view balances, manage funding, and perform transfers. paths: /offline-rates: get: tags: - Hedges description: >- Retrieves offline hedge quote proposals for selected currency pairs. Partners can use these pre-fetched proposals - avoiding the need for a real-time quote per transaction. operationId: Offline Quotes parameters: - description: |- Optional query parameter specifying currency pairs. Multiple pairs can be provided as a comma-separated list. Please encode the query param beforehand. For example, ?pairs=EURUSD%2CGBPEUR represents ?pairs=EURUSD,GBPEUR in: query name: pairs required: false schema: type: string responses: '200': description: Offline Rates Retrieved content: application/json: schema: $ref: '#/components/schemas/GetOfflineRatesResponse' '400': description: >- The request failed because it is not well-formed or is syntactically incorrect or violates schema. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: The request failed because the resource does not exist. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '422': description: >- The request failed because it is either semantically incorrect or has failed business validation. content: application/json: schema: $ref: '#/components/schemas/OfflineRatesInvalidRequestError' '500': description: The request failed because an internal server error occurred. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - api-key: [] components: schemas: GetOfflineRatesResponse: properties: tenorCalculationDate: type: string description: >- Date in ISO 8601 format yyyy-MM-dd. This is the date that will be used to calculate the difference in days between the offline revision creation date and the hedge future endAt date. The difference in days will be used to find the right tenor in the offline table. example: '2023-12-21' validUntilTs: type: number format: double description: >- Unix timestamp of expiration for the specific revision. Indicates the maximum duration during which this revision is valid for accepting hedge requests. example: 1703770471 rates: $ref: '#/components/schemas/IPartnerRatesByTenorResponse' revision: type: number format: double description: >- Unique identifier for the offline rates revision. This id is used later to accept an offline rate. example: 156 required: - tenorCalculationDate - validUntilTs - rates - revision type: object description: >- Represents the response of an offline rates request, including a revision snapshot with a time-to-live (TTL) indicating validity. Rates are organized by currency pair, with each pair associated with rates for various tenors. ErrorResponse: description: An API Error properties: message: type: string description: A short explanation of the error. example: Can't perform this action reason: type: string description: A detailed description of the reason for the failure. example: >- Supplied object is in *Cancelled* state, which prevents performing this action required: - message type: object additionalProperties: false OfflineRatesInvalidRequestError: description: An API Error properties: message: type: string description: A short code of the error. example: CURRENCY_PAIRS_INVALID reason: type: string description: A detailed description of the reason for the failure. example: >- Invalid format for the 'pairs' parameter. Each pair must include two currencies concatenated, and multiple pairs should be comma-separated. eg: EURUSD,GBPUSD required: - message type: object additionalProperties: false IPartnerRatesByTenorResponse: properties: {} additionalProperties: properties: '7': type: number format: double '14': type: number format: double '30': type: number format: double '60': type: number format: double '90': type: number format: double '120': type: number format: double '150': type: number format: double '180': type: number format: double '210': type: number format: double '240': type: number format: double '270': type: number format: double '300': type: number format: double '330': type: number format: double '360': type: number format: double required: - '360' - '330' - '300' - '270' - '240' - '210' - '180' - '150' - '120' - '90' - '60' - '30' - '14' - '7' type: object type: object example: USDEUR: '7': 1.11293728 '14': 1.12093476 '30': 1.10384729 '60': 1.09723456 '90': 1.08576234 '120': 1.07456321 '150': 1.06781234 '180': 1.05678901 '210': 1.0456789 '240': 1.03456789 '270': 1.02345678 '300': 1.01234567 '330': 1.00987654 '360': 0.99876543 USDGBP: '7': 1.27987654 '14': 1.26876543 '30': 1.28123456 '60': 1.29345678 '90': 1.30098765 '120': 1.31456789 '150': 1.32456789 '180': 1.33678901 '210': 1.34789012 '240': 1.35890123 '270': 1.36901234 '300': 1.37123456 '330': 1.38234567 '360': 1.39456789 description: >- Rates information organized by currency pairs and tenors. The structure includes currency pairs as keys, each associated with a nested object containing tenors and corresponding rate. securitySchemes: api-key: type: http scheme: basic description: >- Basic authentication using the partner API keys from https://console.grainfinance.co/keys ````