Syntage DS MX SAT Tax Returns API
The DS MX SAT Tax Returns API from Syntage — 4 operation(s) for ds mx sat tax returns.
OpenAPI Specification
openapi: 3.0.2
info:
version: '2020-06-28'
title: Syntage Accounts Payable Insight DS MX SAT Tax Returns API
contact:
name: Email
email: support@syntage.com
description: "# Introduction\n\nThe Syntage API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer).\nOur API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns [JSON-LD](https://json-ld.org) responses, and uses standard HTTP response codes, authentication, and verbs.\n\n# Environments\n\n| Name | Description | Base URL |\n|------|-------------|----------|\n| **Sandbox** | The Sandbox environment is dedicated to development and testing. In this environment, no real taxpayer credentials are required and all interaction with the SAT is simulated generating life-like data, allowing you to pull test data from all endpoints. | https://api.sandbox.syntage.com |\n| **Production** | The Production environment is dedicated to live applications with real connections to the SAT. In this environment, real taxpayer credentials are required, and you will pull real fiscal data directly from the SAT. | https://api.syntage.com |\n\nEach environment has a different API Key for [authentication](#section/Authentication).\n\n# Request IDs\n\nEach API request has an associated request identifier.\nYou can find this value in the response headers, under `X-Request-ID`:\n\n```curl\ncurl -i https://api.syntage.com\nHTTP/1.1 200 OK\nDate: Sun, 29 Nov 2020 19:21:21 GMT\nX-Request-ID: Root=1-6532dcae-169bf139354cd48959f55c55\n```\n\nIf you need to contact us about a specific request, providing the request identifier will ensure the fastest possible resolution.\n\n# Rate Limiting\n\nOur API employs a number of safeguards against bursts of incoming traffic to help maximize its stability.\nThe returned HTTP headers of any API request show your current rate limit status:\n\n```curl\ncurl -i https://api.syntage.com\nHTTP/1.1 200 OK\nDate: Sun, 29 Nov 2020 19:21:21 GMT\nX-RateLimit-Limit: 60\nX-RateLimit-Remaining: 56\nX-RateLimit-Reset: 1606678044\n```\n\n| Header Name | Description |\n|-----------------------|------------------------------------------------------------------------------|\n| X-RateLimit-Limit | The maximum number of requests you're permitted to make. |\n| X-RateLimit-Remaining | The number of requests remaining in the current rate limit window. |\n| X-RateLimit-Reset | The time at which the current rate limit window resets in UTC epoch seconds. |\n\nIf you exceed the rate limit, a [429 Too Many Requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429) response is returned:\n\n```http\nHTTP/1.1 429 Too Many Requests\nDate: Sun, 29 Nov 2020 19:21:21 GMT\nX-RateLimit-Limit: 60\nX-RateLimit-Remaining: 0\nX-RateLimit-Reset: 1606678044\n```\n\nWe may reduce limits to prevent abuse, or increase limits to enable high-traffic operations.\nYou can check your current limits in the [dashboard](https://app.syntage.com/settings/usage).\nTo request an increased rate limit, please [contact support](https://support.syntage.com/).\n# Pagination\nWhen issuing a GET request on a collection containing more than 1 page (e.g. [/events](#operation/ListEvent)), a collection is returned. Links to the first, the last, previous and the next page in the collection are displayed as well as the number of total items in the collection.\nAll endpoints that support this operation have a query parameter defined by:\n - `itemsPerPage` The number of items per page (default: 20, max: 1000)\n - `page` The collection page number\n\n```bash\n \"hydra:totalItems\": 1,\n \"hydra:view\": {\n \"@id\": \"/events?page=1\",\n \"@type\": \"hydra:PartialCollectionView\",\n \"hydra:first\": \"/events?page=1\",\n \"hydra:next\": \"/events?page=2\",\n \"hydra:last\": \"/events?page=3\"\n },\n```\n## Cursor Pagination\nCursor pagination is a technique used for navigating through large datasets efficiently. It allows you to retrieve a specific subset of results from a collection by using a cursor value that represents the position within the collection. The cursor serves as a reference point for fetching the next or previous set of results.\n### Benefits of Cursor Pagination:\n1. **Efficient Navigation:** Cursor pagination eliminates the need to fetch the entire dataset at once, making it more scalable and faster. You can retrieve data in smaller, manageable chunks based on the cursor values.\n2. **Consistent Results:** Each page of results in cursor pagination is stable and doesn't change even if new items are added or removed from the collection. This ensures that you get consistent and reliable results.\n3. **Flexibility:** Cursors can be used to navigate forwards and backwards in the collection without impacting performance.\n\n### How to Use Cursor Pagination:\nTo use cursor pagination with our API, follow these instructions:\n1. Make a request to retrieve the initial page of results. The response will be a JSON-LD document that includes a `hydra:next` attribute with the URI for the next page. The URI already includes the cursor attribute.\n2. To retrieve the next page of results, make a GET request to the URI provided in the `hydra:next` attribute. This URI will automatically include the cursor value for the next page.\n3. If you want to navigate to the previous page, you can use the `hydra:previous` attribute in the JSON-LD response. It will contain the URI for the previous page, including the cursor value.\n4. You can continue making requests to the `hydra:next` and `hydra:previous` URIs to navigate through the paginated results, based on your requirements.\nMake sure to update your request headers to include the necessary headers for JSON-LD content negotiation, such as `Accept: application/ld+json` or `Content-Type: application/ld+json`.\nBy following these instructions, you can effectively navigate through the paginated results using the cursor values provided in the `hydra:next` and `hydra:previous` attributes, without the need to manually include the cursor in your requests. This simplifies the pagination process and enhances the usability of our API.\n\n### Considerations About Cursor Pagination:\n\n - By default, the API uses offset-based pagination (except for a few endpoints that we will list below). If you want to switch to cursor pagination, you need to include an additional header in your request. Set the `X-Pagination-Style` header with the value `\"cursor\"` to enable cursor pagination. If not specified, the API will assume offset-based pagination.\n\n - After enabling cursor pagination, the API response will no longer include the `hydra:totalItems` field by default. Retrieving the total count can be resource intensive and impact response times, especially for large datasets. However, if you need the `hydra:totalItems` information, you can include an additional header in your request. Set the `X-Pagination-Enable-Partial` header with the value `0` to indicate that the response should include extra information, including the `hydra:totalItems` count. Please be aware that enabling this feature may impact API response times, as the backend needs to perform a count operation on the dataset.\n\nIf you require the `hydra:totalItems` count, please consider the potential impact on API response times.\n### Example\n```bash\n curl -i 'https://api.syntage.com/entities/{entityId}/invoices?itemsPerPage=10' \\\n --header 'Accept: application/ld+json' \\\n --header 'X-Api-Key: {apiKey}' \\\n --header 'X-Pagination-Style: cursor' \\\n --header 'X-Pagination-Enable-Partial: 0'\n```\n**Note:** We only support cursor pagination for the following endpoints:\n - `GET /entities/{entityId}/invoices`\n - `GET /entities/{entityId}/invoices/line-items`\n - `GET /entities/{entityId}/invoices/{invoiceId}/line-items`\n - `GET /invoices/{invoiceId}/line-items`\n - `GET /entities/{entityId}/invoices/payments`\n\nFeel free to reach out if you have any further questions or need additional assistance!\n\n# Property Filtering\nThe property filter adds the possibility to select the properties for GET operations.\nSyntax: `?properties[]=<property>&properties[<relation>][]=<property>`\nYou can add as many properties as you need. The following example shows how to select `paymentType` and `issuer.rfc` when fetching a list of invoices.\n```curl\n curl -i https://api.syntage.com/entities/{entityId}/invoices?properties[]=paymentType&properties[issuer]=rfc\n```\n# Filtering\n**Warning:** Collection endpoints only apply the filter query parameters documented for that endpoint. If you send an unsupported or misspelled filter query parameter, the API ignores it and processes the request as if that parameter was not sent.\n\n# API Versioning Guide\nGuidance on changes between versions.\n## Version: 2020-01-01 to 2020-06-28\n### **Invoice**\n_**Affected Endpoints:** `GET /invoices/{id}` and `GET /entities/{entityId}/invoices`_\n- The `amount` property has been removed from API responses. Use the `total` property instead.\n- Retrieval by invoice's `uuid` at `/invoices/{id}` is now removed. To retrieve an invoice, use the invoice's `id` at the specified endpoint. To find an invoice using its `uuid`, filter the invoice collection at `/entities/{entityId}/invoices?uuid[]={uuid}`.\n- Previously, the `@iri` property for an invoice pointed to the resource using `uuid`, like `/invoices/{uuid}`. Now, it points using its `id`, like `/invoices/{id}`.\n\n### **Entity (Formerly Link)**\n_**Affected Endpoint:** `GET /entities`_\n- Filtering entities by `status` is removed. Use `credential.status` instead. For example, utilize `GET /entities?credential.status[]=active` instead of `GET /entities?status[]=active`.\n\n### **Tax Return**\n_**Affected Endpoints:** `GET /tax-returns/{id}` and `GET /entities/{entityId}/tax-returns`_\n- Retrieval by tax return's `operationNumber` at `/tax-returns/{id}` is removed. To retrieve a tax return, use the tax return's `id` at the mentioned endpoint. To find a tax return using its `operationNumber`, filter the collection at `/entities/{entityId}/tax-returns?operationNumber[]={operationNumber}`.\n- Previously, the `@iri` property for a tax return pointed to the resource using `operationNumber`, like `/tax-returns/{operationNumber}`. Now, it directs to its `id`, like `/tax-returns/{id}`.\n\n### **Event**\n_**Affected Endpoints:** `GET /events` and `GET /events/{id}`_\n- For events associated to an `tax-return`, the `@iri` property now directs to `/tax-returns/{id}` instead of the previous `/tax-returns/{operationNumber}`.\n- For events associated to an `invoice`, the `@iri` property now directs to `/invoices/{id}` instead of the previous `/invoices/{uuid}`.\n\n### **Extraction**\n_**Affected Endpoints:** `GET /extractions` and `GET /extractions/{id}`_\n- The `periodFrom` property has been removed. Use `options.period.from` instead.\n- The `periodTo` property has been removed. Use `options.period.to` instead.\n\n### **File**\n_**Affected Endpoint:** `GET /file/{id}`_\n- For files associated to an `tax-return`, the `@iri` property now directs to `/tax-returns/{id}`, instead of the previous `/tax-returns/{operationNumber}`.\n- For files associated to an `invoice`, the `@iri` property now directs to `/invoices/{id}`, instead of the previous `/invoices/{uuid}`.\n\n### Trying Out This Version\nIf you want to test this version, you can do so by making any request with the `Accept-Version` header pointing to the latest version:\n```curl\n curl -i 'https://api.syntage.com/entities/{entityId}/invoices' \\\n --header 'Accept-Version: 2020-06-28' \\\n --header 'X-Api-Key: {apiKey}'\n```\n"
servers:
- url: https://api.syntage.com
description: Production
- url: https://api.sandbox.syntage.com
description: Sandbox
security:
- ApiKey: []
tags:
- name: DS MX SAT Tax Returns
paths:
/tax-returns/{id}:
get:
tags:
- DS MX SAT Tax Returns
operationId: GetTaxReturn
summary: Retrieve a tax return
description: 'Retrieve a tax return by ID, including filing metadata, payment information, file references, and ISSIF availability.
'
parameters:
- $ref: '#/components/parameters/taxReturnId'
responses:
'200':
$ref: '#/components/responses/TaxReturn'
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
/tax-returns/{id}/pdf:
get:
tags:
- DS MX SAT Tax Returns
operationId: DownloadTaxReturnPdf
summary: Download a tax return PDF
description: 'Download the SAT transcript PDF for a tax return.
'
parameters:
- $ref: '#/components/parameters/taxReturnId'
responses:
'200':
description: Tax return PDF
content:
application/pdf:
schema:
type: string
format: binary
example: <pdf-binary-data>
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
/tax-returns/{id}/data:
get:
tags:
- DS MX SAT Tax Returns
operationId: GetTaxReturnData
summary: Retrieve tax return data
description: 'Retrieve extracted data from a tax return.
For annual tax returns, there are two available formats:
- Financial statements 2022 format - This is available for non-pfae tax returns. Data will only be returned if the SAT provides the XLSX financial statements document.
- Financial statements 2014 format - This is available for pfae annual tax returns from 2014 to now, and all other annual tax returns from 2014-2021, as long as we are able to retrieve the PDF.
For provisional (monthly) tax returns, the response contains extracted financial variables including sales revenue, cash inflow, cash outflow, number of employees, and payroll amount. The available variables depend on the tax regime (601, 612, 626).
The response format here may change if SAT changes the categories or other formatting in the files they provide.
'
parameters:
- $ref: '#/components/parameters/taxReturnId'
responses:
'200':
$ref: '#/components/responses/TaxReturnData'
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
/entities/{entityId}/tax-returns:
get:
tags:
- DS MX SAT Tax Returns
operationId: ListTaxpayerTaxReturn
summary: List an entity's tax returns
description: 'List tax returns extracted for an entity.
'
parameters:
- $ref: '#/components/parameters/entityId'
- name: operationNumber
in: query
description: Filter by operation number (partial match)
schema:
$ref: '#/components/schemas/TaxReturnOperationNumber'
- name: type
in: query
description: Filter by type (exact match)
schema:
$ref: '#/components/schemas/TaxReturnType'
- name: intervalUnit
in: query
description: Filter by interval unit (exact match)
schema:
$ref: '#/components/schemas/TaxReturnIntervalUnit'
- name: complementary
in: query
description: Filter by interval unit (partial match)
schema:
$ref: '#/components/schemas/TaxReturnComplementary'
- name: captureLine
in: query
description: Filter by payment code (partial match)
schema:
$ref: '#/components/schemas/TaxReturnCaptureLine'
- name: period
in: query
description: Filter by period (exact match)
schema:
$ref: '#/components/schemas/TaxReturnPeriod'
- name: presentedAt[before]
in: query
description: Filter by filing date (less than or equal `<=`)
schema:
$ref: '#/components/schemas/TaxReturnPresentedAt'
- name: presentedAt[strictly_before]
in: query
description: Filter by filing date (less than `<`)
schema:
$ref: '#/components/schemas/TaxReturnPresentedAt'
- name: presentedAt[after]
in: query
description: Filter by filing date (greater than or equal `>=`)
schema:
$ref: '#/components/schemas/TaxReturnPresentedAt'
- name: presentedAt[strictly_after]
in: query
description: Filter by filing date (greater than `>`)
schema:
$ref: '#/components/schemas/TaxReturnPresentedAt'
- name: fiscalYear
in: query
description: Filter by fiscal year (exact match)
schema:
$ref: '#/components/schemas/TaxReturnFiscalYear'
- name: order[period]
in: query
description: Order by period
schema:
$ref: '#/components/schemas/CollectionOrder'
- name: order[presentedAt]
in: query
description: Order by filing date
schema:
$ref: '#/components/schemas/CollectionOrder'
- $ref: '#/components/parameters/collectionCursorNextPageParam'
- $ref: '#/components/parameters/collectionCursorPreviousPageParam'
- $ref: '#/components/parameters/collectionLimit'
responses:
'200':
$ref: '#/components/responses/TaxpayerTaxReturnCollection'
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
components:
responses:
TaxpayerTaxReturnCollection:
description: Taxpayer tax return collection response
content:
application/ld+json:
schema:
$ref: '#/components/schemas/TaxpayerTaxReturnCollection'
TaxReturnData:
description: Extracted data from tax returns
content:
application/json:
schema:
type: object
examples:
financial_statements_2022:
summary: Financial statements 2022 format
value:
ESTADO DE RESULTADOS:
Pérdida neta:
Notas: This field may contains a comment from the respective line
Total: 123
Partes Relacionadas: null
Partes No Relacionadas: null
Utilidad neta:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Ingresos Netos:
Notas: null
Total: 123
Sin Ingresos:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Otros Ingresos:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Primas cedidas:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Primas emitidas:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Partes Relacionadas: 0
Gastos por intereses:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Ingresos por intereses:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Partes No Relacionadas: 123
Ventas y/o servicios nacionales:
Notas: null
Total: 123
Partes Relacionadas: 0
Partes No Relacionadas: 123
Ventas y/o servicios extranjeros:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Estimación preventiva para riesgos crediticios:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Devoluciones, descuentos y bonificaciones nacionales:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Devoluciones, descuentos y bonificaciones extranjeras:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Estimación preventiva para riesgos crediticios (Recuperaciones):
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Pérdida Bruta:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Utilidad Bruta:
Notas: null
Total: 123
Partes Relacionadas: null
Partes No Relacionadas: null
Costo de ventas:
Notas: null
Total: 123
Maquilas:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Otros costos:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Gastos Indirectos:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Partes Relacionadas: 0
Sin Costo de ventas:
Notas: null
Total: 0
Partes Relacionadas: 0
Partes No Relacionadas: 0
Partes No Relacionadas: 123
Deducciones de inversiones:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Mano de obra directa de fabricación:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Gastos relacionados a la mano de obra:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Mano de obra indirecta de fabricación:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Costo de servicios:
Notas: null
Total: 0
Costo de servicios:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Partes Relacionadas: 0
Partes No Relacionadas: 0
Sin Costo de servicios:
Notas: null
Total: 0
Partes Relacionadas: 0
Partes No Relacionadas: 0
Costo neto de adquisición:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Comisiones y tarifas pagadas:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Comisiones y tarifas cobradas:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Otros ingresos (egresos) de la operación:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Incremento neto de otras reservas técnicas:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Costo neto de siniestralidad, reclamaciones y otras obligaciones pendientes de cumplir:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Incremento neto de las reservas técnicas (Riesgos en curso, obligaciones pendientes de cumplir, riesgos catastróficos):
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Gastos de operación:
Notas: null
Total: 123
Gastos de venta:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Gastos generales:
Notas: null
Total: 123
Partes Relacionadas: 0
Partes No Relacionadas: 123
Partes Relacionadas: 0
Partes No Relacionadas: 123
Sin Gastos de operación:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Gastos de administración:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Pérdida de operación:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Utilidad de operación:
Notas: null
Total: 123
Partes Relacionadas: null
Partes No Relacionadas: null
Impuestos a la utilidad:
Notas: null
Total: 0
Partes Relacionadas: 0
Partes No Relacionadas: 0
Impuesto sobre la renta:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Sin Impuestos a la utilidad:
Notas: null
Total: 0
Partes Relacionadas: 0
Partes No Relacionadas: 0
Impuesto sobre la renta diferido:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Operaciones discontinuadas:
Notas: null
Total: 0
Partes Relacionadas: 0
Partes No Relacionadas: 0
Operaciones discontinuadas:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Sin Operaciones discontinuadas:
Notas: null
Total: 0
Partes Relacionadas: 0
Partes No Relacionadas: 0
Pérdida de enajenación de acciones:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Utilidad de enajenación de acciones:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Participación de los Trabajadores en las Utilidades:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Pérdida de segmento del negocio o segmento geográfico:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Utilidad de segmento del negocio o segmento geográfico:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Participación en asociadas:
Notas: null
Total: 0
Partes Relacionadas: 0
Partes No Relacionadas: 0
Sin Participación en asociadas:
Notas: null
Total: 0
Partes Relacionadas: 0
Partes No Relacionadas: 0
Pérdida neta por participación en los resultados de subsidiarias no consolidadas, asociadas y negocios conjuntos:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Utilidad neta por participación en los resultados de subsidiarias no consolidadas, asociadas y negocios conjuntos:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Pérdida de operaciones continuas:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Utilidad de operaciones continuas:
Notas: null
Total: 123
Partes Relacionadas: null
Partes No Relacionadas: null
Resultado Integral de Financiamiento:
Notas: null
Total: 0
Ganancia cambiaria:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Gastos Financieros:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Pérdida cambiaria:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Partes Relacionadas: 0
Productos Financieros:
Notas: null
Total: null
Partes Relacionadas: null
Partes No Relacionadas: null
Partes No Relacionadas: 0
Intereses devengados a cargo nacionales:
Notas: null
Total: null
Partes Relacionadas: n
# --- truncated at 32 KB (87 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/syntage/refs/heads/main/openapi/syntage-ds-mx-sat-tax-returns-api-openapi.yml