openapi: 3.0.1
info:
title: Public Account Pairing Endpoints Finance Endpoints API
description: "# Overview\n\nThe API endpoints are developed around [RESTful](https://en.wikipedia.org/wiki/Representational_state_transfer) principles secure via the OAuth2.0 protocol.\n\nBeyond the entry points, the API also provides a line of communication into your system via [webhooks](https://en.wikipedia.org/wiki/Webhook).\n\nFor testing purposes, we offer a staging environment. Also, more detailed information about the business rules and workflows can be found on the [**Documentation Section**](/docs/)\n\n## Versioning\nEach API is versioned individually, but we follow these rules:\n- Non breaking changes (eg: adding new fields) are added in the current version without previous communication\n- Breaking changes (fields removal, semantic changed or schema update) have the version incremented\n- Users will be notified about new versions and will be given time to migrate (the time will be set on a case by case basis)\n- Once users migrate to the new version, we will deprecate the old ones\n- Once there is a new version for an API, we won't accept new integrations targeting old versions\n\n## API General Definitions\nThe APIs use resource-oriented URLs communicating, primarily, via JSON and leveraging the HTTP headers, [response status codes](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status), and verbs.\n\nTo exemplify how the API is to be consumed, consider a fake GET resource endpoint invocation below:\n\n```\ncurl --request GET 'https://{{public-api-url}}/v1/resource/123' \\\n--header 'Authorization: Bearer 34fdabeeafds=' --header 'X-Store-Id: 321'\n```\n\n| Header | Description |\n| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n|`Authorization` | Standard HTTP header is used to associate the request with the originating invoker. The content of this header is a `Bearer` token generated from you client_secret, defined in the [API Auth](#/section/Guides/API-Auth) guide.|\n|`X-Store-Id` | The ID of the store in your system this call acts on behalf of. |\n\n_All resource endpoints expect the `Authorization` header, the remaining headers are explicitly stated in the individual endpoint documentation section._\n\nWith these headers, the system will:\n - Validate the client token, making sure the call is originating from a trusted source.\n - Validate that the Application has the permission to access the `v1/resource/{id}` resource via the Application's pre-configured scopes.\n - Translate your X-Store-Id to our internal store ID (e.g. `AAA`).\n - Validate and retrieve resource `AAA`, that is associated to your Application via store id `321`.\n\nPOST/PUT methods will look similar to the GET calls, but they'll take in a body in the HTTP request (default to the application/json content-type).\n\n```\ncurl --location --request POST 'https://{{public-api-url}}/v1/resource' \\\n--header 'Authorization: Bearer 34fdabeeafds=' --header 'X-Store-Id: 321'\n--data '{\"foo\": \"bar\"}'\n```\n\n## API Authentication/Authorization\n\n<SecurityDefinitions />\n\n## Webhook\n\nThe Public API is able to send notifications to your system via HTTP POST requests.\n\nEvery webhook is signed using HMAC-SHA256 that is present in the header `X-HMAC-SHA256`, and you can also authenticate the requests using Basic Auth, Bearer Token or HMAC-SHA1 (legacy). Please, refer to [**Webhook Authentication Guide**](/docs/guides-webhook-authentication/) for more details.\n\n_Please work with your Account Representative to setup your Application's Webhook configurations._\n\n```\nExample Base-URL = https://{{your-server-url}}/webhook\n```\n\n### Notification Schema\n\n| **Name** | **Type** | **Description** |\n| ------------------------| ---------| -------------------------------------------------------------------- |\n| eventId | string | Unique id of the event. |\n| eventTime | string | The time the event occurred. |\n| eventType | string | The type of event (e.g. create_order). |\n| metadata.storeId | string | Id of the store for which the event is being published. |\n| metadata.applicationId | string | Id of the application for which the event is being published. |\n| metadata.resourceId | string | The external identifier of the resource that this event refers to. |\n| metadata.resourceHref | string | The endpoint to fetch the details of the resource. |\n| metadata.payload | object | The event object which will be detailed in each Webhook description. |\n\n### Notification Request Example\n\n```\ncurl --location --request POST 'https://{{your-server-url}}/webhook' \\\n--header 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36' \\\n--header 'Authorization: MAC <hash signature>' \\\n--header 'Content-Type: application/json' \\\n--data-raw '{\n \"eventId\": \"123456\",\n \"eventTime\": \"2020-10-10T20:06:02:123Z\",\n \"eventType\": \"orders.new_order\",\n \"metadata\": {\n \"storeId\": \"755fd19a-7562-487a-b615-171a9f89d669\",\n \"applicationId\": \"e22f94b3-967c-4e26-bf39-9e364066b68b\",\n \"resourceHref\": \"https://{{public-api-url}}/v1/orders/bf9f1d81-f213-496e-a026-91b6af44996c\",\n \"resourceId\": \"bf9f1d81-f213-496e-a026-91b6af44996c\",\n \"payload\": {}\n }\n}\n```\n\n### Expected Response\n\nThe partner application should return an HTTP 200 response code with an empty response body to acknowledge receipt of the webhook event.\n## Rate Limiting\nPlease, refer to [**Rate Limiting Guide**](/docs/guides-rate-limiting/) for more details.\n\n## Error codes\nThe APIs use standard HTTP status codes to indicate the success or failure of a request. Error codes are divided into two categories: 4XX codes for client-side errors and 5xx codes for server-side errors.\n### 4XX Client-Side Errors\nClient-side errors are indicated by status codes in the 4xx range. These errors are typically the result of a problem with the request made by your application.\nIf a client-side error occurs, our API will return a response that includes an appropriate error message. This message will provide information about the cause of the error. The aim of these messages is to assist you in identifying and resolving the issue.\nFor example, if you submit a request with missing or invalid parameters, you might receive a 400 Bad Request error with a message indicating which parameters were missing or incorrect.\n### 5XX Server-Side Errors\nServer-side errors are represented by status codes in the 5xx range. These errors suggest a problem with our server, not with your application's request.\nServer-side errors are typically transient, meaning they are temporary. If a server-side error occurs, we recommend that the client retries the same request with the exact same parameters.\nFor example, if you get a 500 Internal Server Error, it's possible that our server is suffering a temporary problem. In such cases, retrying the request after a short delay is often successful.\nIf you continually receive server-side errors, reach out to our support team for further assistance."
version: v1
license:
name: Proprietary
contact:
name: Kin Lane
email: kin@apievangelist.com
x-generated-from: documentation
x-source-url: https://developer-guides.tryotter.com/api-reference/
x-last-validated: '2026-06-03'
servers:
- url: https://{public-api-url}/
description: Otter Public API base URL. The concrete host is provisioned per integration partner/account via your Otter account representative; substitute the value provided during onboarding.
variables:
public-api-url:
default: public-api-url
description: Account-specific Public API host provided by Otter during onboarding.
tags:
- name: Finance Endpoints
description: Endpoints to handle financial data.
x-displayName: Finance
paths:
/finance/v1/financial-transactions:
post:
tags:
- Finance Endpoints
summary: Otter Post Financial Transactions
operationId: postFinancialTransactions
description: Post financial data related to a given order.
parameters:
- $ref: '#/components/parameters/storeIdHeader'
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/FinancialTransaction'
examples:
PostFinancialTransactionsRequestExample:
summary: Default postFinancialTransactions request
x-microcks-default: true
value:
orderIdentifiers:
id: 69f60a06-c335-46d9-b5a1-97f1a211c514
source: ubereats
id: store_123
pending: true
currencyCode: EUR
createdAt: '2007-12-03T10:15:30+01:00'
customerId: store_123
notes: string
type: PAYMENT
payout:
id: store_123
date: '2021-10-01'
orderItems:
- id: store_123
name: Sample Name
issues:
- {}
issues:
- type: MISSING_ITEM
data:
foodSales: {}
feeForRestaurantProvidedDelivery: {}
restaurantFundedDiscount: {}
voucherDiscount: {}
promotionDiscount: {}
operatorDiscount: {}
loyaltyDiscount: {}
tipForRestaurant: {}
adjustments: {}
packingFee: {}
bagFee: {}
serviceProviderDiscount: {}
tipForServiceProviderCourier: {}
feeForServiceProviderDelivery: {}
smallOrderFee: {}
serviceFee: {}
otherFee: {}
netPayout: {}
couponCodes:
- TACOWED5OFF
required: true
responses:
'202':
description: The financial transaction for the order was successfully processed.
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
'404':
$ref: '#/components/responses/404'
'422':
$ref: '#/components/responses/422'
security:
- OAuth2.0:
- finance
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
/finance/v1/financial-invoices:
post:
tags:
- Finance Endpoints
summary: Otter Post a Financial Invoice
operationId: postFinancialInvoice
description: Post a financial invoice containing payout and financial data for orders in a given period of time.
parameters:
- $ref: '#/components/parameters/storeIdHeader'
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/FinancialInvoice'
examples:
PostFinancialInvoiceRequestExample:
summary: Default postFinancialInvoice request
x-microcks-default: true
value:
sourceService: ubereats
payout:
id: store_123
date: '2021-10-01'
summary: {}
total: 19.07
financialTransactions:
- orderIdentifiers: {}
id: store_123
createdAt: '2007-12-03T10:15:30+01:00'
customerId: store_123
notes: string
type: PAYMENT
orderItems:
- {}
issues:
- {}
data: {}
currencyCode: EUR
required: true
responses:
'202':
description: The financial transaction for the order was successfully processed.
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
'404':
$ref: '#/components/responses/404'
'422':
$ref: '#/components/responses/422'
security:
- OAuth2.0:
- finance
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
components:
parameters:
storeIdHeader:
name: X-Store-Id
in: header
required: true
schema:
$ref: '#/components/schemas/StoreId'
schemas:
OrderItemInformation:
required:
- id
type: object
properties:
id:
type: string
description: Regular item identifier.
example: store_123
name:
type: string
nullable: true
description: Item name
example: Sample Name
issues:
type: array
nullable: true
description: Order issues that relate to this item.
items:
$ref: '#/components/schemas/OrderIssue'
ErrorDetail:
type: object
properties:
attribute:
type: string
description: The error attribute.
example: Order Currency Code
message:
type: string
description: The error detail description.
example: Order Currency Code must be exactly 3 characters
description: The error detail response object.
ErrorMessage:
type: object
properties:
message:
type: string
description: The error description.
example: The request body is invalid.
details:
type: array
description: The error details.
items:
$ref: '#/components/schemas/ErrorDetail'
description: The error response object.
CompositeFinanceLine:
required:
- breakdown
type: object
properties:
breakdown:
type: array
minItems: 1
description: Breakdown values for the finance line.
items:
$ref: '#/components/schemas/SimpleFinanceLine'
description: composite finance line can represent a value, tax and VAT for a given line as a list of SimpleFinanceLine objects
FinancialInvoice:
required:
- payout
- financialTransactions
type: object
properties:
sourceService:
type: string
nullable: true
description: Describes the source of the order, typically from a food ordering marketplace.
example: ubereats
payout:
$ref: '#/components/schemas/InvoicePayoutInfo'
financialTransactions:
type: array
description: List of financial transactions related to this invoice.
items:
$ref: '#/components/schemas/SimpleFinancialTransaction'
currencyCode:
maxLength: 3
minLength: 3
type: string
description: The 3-letter currency code (ISO 4217) to use for all monetary values in this order.
example: EUR
OrderIdentifierFinance:
required:
- id
type: object
properties:
id:
type: string
description: Unique ID for the order that was placed.
example: 69f60a06-c335-46d9-b5a1-97f1a211c514
source:
type: string
nullable: true
description: Describes the source of the order, typically from a food ordering marketplace.
example: ubereats
description: The external identifiers of the order.
FinancialTransaction:
required:
- id
- orderIdentifiers
- pending
- currencyCode
- createdAt
- type
- data
type: object
properties:
orderIdentifiers:
$ref: '#/components/schemas/OrderIdentifierFinance'
id:
type: string
description: External financial transaction identifier.
example: store_123
pending:
type: boolean
description: Whether the transaction can be updated in the future.
example: true
currencyCode:
maxLength: 3
minLength: 3
type: string
description: The 3-letter currency code (ISO 4217) to use for all monetary values in this order.
example: EUR
createdAt:
type: string
description: The date (in UTC) when the financial transaction was created.
format: date-time
example: '2007-12-03T10:15:30+01:00'
customerId:
type: string
nullable: true
description: Customer identifier.
example: store_123
notes:
type: string
nullable: true
description: General notes about the financial transaction.
example: string
type:
type: string
description: Financial transaction operation type.
enum:
- PAYMENT
- ADJUSTMENT
- CANCELLATION
- MISC
example: PAYMENT
payout:
nullable: true
$ref: '#/components/schemas/PayoutInfo'
orderItems:
type: array
nullable: true
description: Detailed financial per order item.
items:
$ref: '#/components/schemas/OrderItemInformation'
issues:
type: array
nullable: true
description: List of issues that might have happened with the order.
items:
$ref: '#/components/schemas/OrderIssue'
data:
$ref: '#/components/schemas/FinancialData'
SimpleFinancialTransaction:
required:
- id
- orderIdentifiers
- createdAt
- type
- data
type: object
properties:
orderIdentifiers:
$ref: '#/components/schemas/SimpleOrderIdentifierFinance'
id:
type: string
description: External financial transaction identifier.
example: store_123
createdAt:
type: string
description: The date (in UTC) when the financial transaction was created.
format: date-time
example: '2007-12-03T10:15:30+01:00'
customerId:
type: string
nullable: true
description: Customer identifier.
example: store_123
notes:
type: string
nullable: true
description: General notes about the financial transaction.
example: string
type:
type: string
description: Financial transaction operation type.
enum:
- PAYMENT
- ADJUSTMENT
- CANCELLATION
- MISC
example: PAYMENT
orderItems:
type: array
nullable: true
description: Detailed financial per order item.
items:
$ref: '#/components/schemas/OrderItemInformation'
issues:
type: array
nullable: true
description: List of issues that might have happened with the order.
items:
$ref: '#/components/schemas/OrderIssue'
data:
$ref: '#/components/schemas/FinancialData'
SimpleFinanceLine:
required:
- subType
- name
- value
type: object
properties:
subType:
type: string
nullable: false
enum:
- VALUE
- TAX
- VALUE_WITH_TAX
- VAT
description: type of the finance line.
example: VALUE
name:
type: string
nullable: false
description: name of the finance line.
example: sales tax.
value:
type: number
nullable: false
description: money amount.
example: 3.4
description: simple finance line.
SimpleOrderIdentifierFinance:
required:
- id
type: object
properties:
id:
type: string
description: Unique ID for the order that was placed.
example: 69f60a06-c335-46d9-b5a1-97f1a211c514
description: The external identifiers of the order.
InvoicePayoutInfo:
required:
- id
- date
type: object
properties:
id:
type: string
description: Payout identifier.
example: store_123
date:
type: string
description: The payout date.
format: date
example: '2021-10-01'
summary:
$ref: '#/components/schemas/FinancialData'
total:
type: number
nullable: true
description: Total payout value. Should only be used if summary is not provided.
example: 19.07
FinancialData:
required:
- foodSales
type: object
properties:
foodSales:
nullable: false
description: Breakdown of the total value of items within the order.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
feeForRestaurantProvidedDelivery:
nullable: true
description: Extra charge to the customer when order is delivered by the store itself.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
restaurantFundedDiscount:
nullable: true
description: Discount funded by the restaurant.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
voucherDiscount:
nullable: true
description: Discount provided by voucher.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
promotionDiscount:
nullable: true
description: Discount provided by item promotion.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
operatorDiscount:
nullable: true
description: Discount provided by operator when the order was placed.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
loyaltyDiscount:
nullable: true
description: Discount provided by loyalty programs.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
tipForRestaurant:
nullable: true
description: Tip for the restaurant.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
adjustments:
nullable: true
description: Any adjustments that may happen to the order total value.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
packingFee:
nullable: true
description: Fee charged to the customer for the process of packing and fulfilling the order.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
bagFee:
nullable: true
description: Fee charged to the customer for providing bags for the order.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
serviceProviderDiscount:
nullable: true
description: Discount funded by the service provider (order source).
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
tipForServiceProviderCourier:
nullable: true
description: Tip for the courier from the service provider.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
feeForServiceProviderDelivery:
nullable: true
description: Fee charged to the customer for a delivery provided by the service provider.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
smallOrderFee:
nullable: true
description: Fee charged to the customer when the order value is less than the minimum value.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
serviceFee:
nullable: true
description: Any service fees charged by the service provider to the customer.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
otherFee:
nullable: true
description: All the extra costs that the customer has to pay, are different from tips, delivery fees, bag fees, packing fees, and service fees.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
netPayout:
nullable: true
description: The net payout received by the store.
allOf:
- $ref: '#/components/schemas/CompositeFinanceLine'
couponCodes:
nullable: true
type: array
items:
type: string
description: Any codes entered by the customer at order checkout.
example:
- TACOWED5OFF
description: "Breakdown of order values. Represents total values, fees, discounts, and any possible adjustments that may happen in the order value.\n\nBreakdown lists can be used to represent aggregate values (e.g. order total value) or, when available, can accurately represent the values of each item/fee/tax/charges related to the order.\n\nAll objects in breakdown lists have a required property \"subType\". Allowed values are:\n\n**VALUE**: represent the net value of the order/item/fee. Should be used in the following cases:\n - when the amount does not contain taxes or VAT\n - when tax/VAT is a known value, in that case, the list must contain an object with subtype TAX or VAT representing this value.\n\n**TAX**: represent the tax value for the order/item/fee. Should be used when tax amount is available, in that case, this information should be part of the breakdown list with the \"VALUE\" as the net amount, example below:\n\n\n ```\n \"breakdown\": [\n {\n \"name\": \"Item 1\",\n \"value\": 10,\n \"subType\": \"VALUE\"\n },\n {\n \"name\": \"Item 1 - Tax\",\n \"value\": 2,\n \"subType\": \"TAX\"\n }\n ]\n ```\n\n\n**VAT**: represents the amount for value-added tax. Should be used when the order/item/fee contains VAT. In that case, this information should be part of the breakdown list with the \"VALUE\" as net amount, example below:\n\n\n ```\n \"breakdown\": [\n {\n \"name\": \"Item 1\",\n \"value\": 12,\n \"subType\": \"VALUE\"\n },\n {\n \"name\": \"Item 1 - Tax\",\n \"value\": 2,\n \"subType\": \"VAT\"\n }\n ]\n ```\n\n\n**VALUE_WITH_TAX**: represents the gross value of the order/item/fee. Should be used when the value includes tax/VAT and values related to taxation are not available.\n\n\n ```\n \"breakdown\": [\n {\n \"name\": \"Item 1\",\n \"value\": 12,\n \"subType\": \"VALUE_WITH_TAX\"\n }\n ]\n ```"
OrderIssue:
required:
- type
type: object
properties:
type:
type: string
description: Order issue type.
enum:
- MISSING_ITEM
- INCOMPLETE
- WRONG_INGREDIENTS
- WRONG_SIZE
- WRONG_INSTRUCTIONS
- TEMPERATURE_COLD
- WRONG_ORDER
- POOR_QUALITY
- HANDLED_POORLY
- WRONG_ITEM
- WRONG_QUANTITY
- LATE_TO_COURIER
example: MISSING_ITEM
StoreId:
type: string
description: The unique identifier of the store in the partner application. This ID, along with the `Application ID`, will be used to match the correct store when performing operations. It cannot be longer than 255 characters and must only contain printable ASCII characters. During on-boarding, this ID will be similar to `onboarding:905bb725-b141-4a9b-832a-1f254f772c94` (where the UUID is the Internal Store ID). During off-boarding, this field will be filled with the last known Store ID, or with an empty string, in case none is found. In that case, please fall back to the provided `internalStoreId` (a.k.a. Sku-Sku ID).
example: partner-store-unique-identifier
PayoutInfo:
required:
- id
- date
type: object
properties:
id:
type: string
description: Payout identifier.
example: store_123
date:
type: string
description: The payout date.
format: date
example: '2021-10-01'
responses:
'422':
description: The request body is not valid.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
'400':
description: The request is malformed.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
'403':
description: Authorization not valid for the requested resource.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
'404':
description: Resource not found.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
'401':
description: Invalid authorization.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorMessage'
securitySchemes:
OAuth2.0:
type: oauth2
description: "The **Authorization API** is based on the [OAuth2.0 protocol](https://tools.ietf.org/html/rfc6749), supporting the (Client Credentials)[https://datatracker.ietf.org/doc/html/rfc6749#section-4.4] and the (Authorization Code)[https://datatracker.ietf.org/doc/html/rfc6749#section-4.1] flows. Resources expect a valid token sent as a `Bearer` token in the HTTP `Authorization` header.\n### Scopes\nScopes must be configured by our internal team to be enabled for an app. Once the scopes are configured they can be enabled on the Application Settings Page in Developer Portal. Each endpoint requires a given scope that can be verified on each endpoint documentation. When generating an OAuth2.0 token multiple scopes can be requested.\n\n### Authorization Code Flow\nTo perform this flow, the authorization code flow must be enabled in the Application Settings Page in Developer Portal. When enabling the flow it is mandatory to provide a redirect URI pointing to your application. Once the flow is complete we will redirect the user to this URI passing the 'code' and 'state' parameters.\nThe Authorization Code flow provides a temporary code that the client application can exchange for an access token. To start the flow the application must request the user authorization. This is done by sending a request to https://{{public-api-url}}/v1/auth/oauth2/authorize.\nExample\n```\ncurl --location 'https://{{public-api-url}}/v1/auth/oauth2/authorize?client_id=[CLIENT_ID]&redirect_uri=[REDIRECT_URI]&response_type=code&scope=organization.read&state=8A9D16B4C3E25F6A'\n```\nThis call will return a 302 redirecting the user to our authorization page. If the user approves the application, we will redirect to configured URI passing the authorization code in the query parameter 'code'. The 'state' parameter is also sent to ensure the source of the data.\nWith the authorization code, the client application can generate the token.\n### Client Credentials Flow\nThe client_credentials flow does not require any steps before generating the token. Once your application is ready, and the client_id and client_secret are available, the token can be generated by following the instructions in the next section.\n\n### Generate Token\nTo generate the token, use the `Client ID` and `Client Secret` (provided during onboarding), and optionally the authorization code obtained after performing the Autho
# --- truncated at 32 KB (83 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/otter/refs/heads/main/openapi/otter-finance-endpoints-api-openapi.yml