Syntage Financial Ratios Insight API
The Financial Ratios Insight API from Syntage — 1 operation(s) for financial ratios insight.
OpenAPI Specification
openapi: 3.0.2
info:
version: '2020-06-28'
title: Syntage Accounts Payable Insight Financial Ratios Insight 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: Financial Ratios Insight
paths:
/entities/{entityId}/insights/financial-ratios:
get:
tags:
- Financial Ratios Insight
operationId: GetFinancialRatiosInsight
summary: Get financial ratios
description: Liquidity, leverage, profitability, and efficiency ratios computed per fiscal year from the entity's annual tax filings.
parameters:
- $ref: '#/components/parameters/entityId'
- name: options[from]
in: query
description: Filter by invoice issuing date (greater than)
schema:
type: string
format: date-time
- name: options[to]
in: query
description: Filter by invoice issuing date (less than)
schema:
type: string
format: date-time
responses:
'200':
description: Financial Ratios
content:
application/ld+json:
schema:
type: object
properties:
data:
type: object
properties:
liquidity:
type: object
properties:
current_ratio:
type: object
properties:
'2014':
type: number
example: 2.170153630241602
'2015':
type: number
example: 3.9382332732421896
'2016':
type: number
example: 1.4433204505794686
'2017':
type: number
example: 1.4715106437701448
'2018':
type: number
example: 1.1730789739846177
'2019':
type: number
example: 2.3687243725981255
'2020':
type: number
example: 1.3305483243873792
quick_ratio:
type: object
properties:
'2014':
type: number
example: 1.8293385448664694
'2015':
type: number
example: 3.292934792905369
'2016':
type: number
example: 1.2009179843461073
'2017':
type: number
example: 1.1939344402370429
'2018':
type: number
example: 0.9524613210383901
'2019':
type: number
example: 2.047362926655386
'2020':
type: number
example: 1.165771941991342
cash_ratio:
type: object
properties:
'2014':
type: number
example: 0.8457322529202494
'2015':
type: number
example: 0.9863829458972141
'2016':
type: number
example: 0.4934330804148122
'2017':
type: number
example: 0.5376921355145503
'2018':
type: number
example: 0.357758593415979
'2019':
type: number
example: 0.7029122106845779
'2020':
type: number
example: 0.4280589983565223
cash_to_assets:
type: object
properties:
'2014':
type: number
example: 0.8457322529202494
'2015':
type: number
example: 0.9863829458972141
'2016':
type: number
example: 0.4934330804148122
'2017':
type: number
example: 0.5376921355145503
'2018':
type: number
example: 0.357758593415979
'2019':
type: number
example: 0.7029122106845779
'2020':
type: number
example: 0.4280589983565223
net_working_capital_to_sales:
type: object
properties:
'2014':
type: number
example: 0.8457322529202494
'2015':
type: number
example: 0.9863829458972141
'2016':
type: number
example: 0.4934330804148122
'2017':
type: number
example: 0.5376921355145503
'2018':
type: number
example: 0.357758593415979
'2019':
type: number
example: 0.7029122106845779
'2020':
type: number
example: 0.4280589983565223
activity:
type: object
properties:
total_asset_turnover:
type: object
properties:
'2014':
type: number
example: 0.7571560970807056
'2015':
type: number
example: 0.7877245363542329
'2016':
type: number
example: 2.3693977000910613
'2017':
type: number
example: 0.6628963317110973
'2018':
type: number
example: 0.8299941484739886
'2019':
type: number
example: 1.3275331009476332
'2020':
type: number
example: 0.5645231967194583
inventory_turnover:
type: object
properties:
'2014':
type: number
example: 0.9355785151784264
'2015':
type: number
example: 0.7176644321323731
'2016':
type: number
example: 1.828113585829089
'2017':
type: number
example: 0.7805613367433604
'2018':
type: number
example: 0.6717572448950851
'2019':
type: number
example: 1.8946440989913522
'2020':
type: number
example: 0.7171407160576209
fixed_asset_turnover_ratio:
type: object
properties:
'2014':
type: number
example: 0.9355785151784264
'2015':
type: number
example: 0.7176644321323731
'2016':
type: number
example: 1.828113585829089
'2017':
type: number
example: 0.7805613367433604
'2018':
type: number
example: 0.6717572448950851
'2019':
type: number
example: 1.8946440989913522
'2020':
type: number
example: 0.7171407160576209
sales_to_capital_employed:
type: object
properties:
'2014':
type: number
example: 0.9355785151784264
'2015':
type: number
example: 0.7176644321323731
'2016':
type: number
example: 1.828113585829089
'2017':
type: number
example: 0.7805613367433604
'2018':
type: number
example: 0.6717572448950851
'2019':
type: number
example: 1.8946440989913522
'2020':
type: number
example: 0.7171407160576209
accounts_payable_payment_period:
type: object
properties:
'2014':
type: number
example: 0.9355785151784264
'2015':
type: number
example: 0.7176644321323731
'2016':
type: number
example: 1.828113585829089
'2017':
type: number
example: 0.7805613367433604
'2018':
type: number
example: 0.6717572448950851
'2019':
type: number
example: 1.8946440989913522
'2020':
type: number
example: 0.7171407160576209
accounts_receivable_collection_period:
type: object
properties:
'2014':
type: number
example: 0.9355785151784264
'2015':
type: number
example: 0.7176644321323731
'2016':
type: number
example: 1.828113585829089
'2017':
type: number
example: 0.7805613367433604
'2018':
type: number
example: 0.6717572448950851
'2019':
type: number
example: 1.8946440989913522
'2020':
type: number
example: 0.7171407160576209
profitability:
type: object
properties:
return_on_assets:
type: object
properties:
'2014':
type: number
example: 0.8909660418010791
'2015':
type: number
example: 0.9170198717865244
'2016':
type: number
example: 0.8867081841792085
'2017':
type: number
example: 0.8763975270414898
'2018':
type: number
example: 0.7464401447048928
'2019':
type: number
example: 0.8589579515876329
'2020':
type: number
example: 0.8023060035397855
return_on_equity:
type: object
properties:
'2014':
type: number
example: 1.2206153800050163
'2015':
type: number
example: 0.9472091208246147
'2016':
type: number
example: 0.8345801104504675
'2017':
type: number
example: 1.4492972599256255
'2018':
type: number
example: 0.5783242083326875
'2019':
type: number
example: 1.0231983929814674
'2020':
type: number
example: 0.8401368179614076
return_on_sales:
type: object
properties:
'2014':
type: number
example: 1.1767270252941127
'2015':
type: number
example: 1.1641377530661918
'2016':
type: number
example: 0.37423358018163444
'2017':
type: number
example: 1.3220732792098786
'2018':
type: number
example: 0.8993318158655498
'2019':
type: number
example: 0.6470331707544488
'2020':
type: number
example: 1.4212099842878454
gross_profit_margin:
type: object
properties:
'2014':
type: number
example: 1.267320660225698
'2015':
type: number
example: 1.0523144011638075
'2016':
type: number
example: 0.5410234037399851
'2017':
type: number
example: 1.0225926594543397
'2018':
type: number
example: 1.2427611679673494
'2019':
type: number
example: 0.6312249227085254
'2020':
type: number
example: 1.5823179451948328
return_on_investment:
type: object
properties:
'2014':
type: number
example: 1.1767270252941127
'2015':
type: number
example: 1.1641377530661918
'2016':
type: number
example: 0.37423358018163444
'2017':
type: number
example: 1.3220732792098786
'2018':
type: number
example: 0.8993318158655498
'2019':
type: number
example: 0.6470331707544488
'2020':
type: number
example: 1.4212099842878454
leverage:
type: object
properties:
total_debt_ratio:
type: object
properties:
'2014':
type: number
example: 0.2700681505443447
'2015':
type: number
example: 0.03187178878916228
'2016':
type: number
example: -0.062460239677416485
'2017':
type: number
example: 0.3952948430424381
'2018':
type: number
example: -0.29069496650829235
'2019':
type: number
example: 0.16051671163718226
'2020':
type: number
example: 0.04502934952121079
debt_equity_ratio:
type: object
properties:
# --- truncated at 32 KB (38 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/syntage/refs/heads/main/openapi/syntage-financial-ratios-insight-api-openapi.yml