Sources & Integrations

Sintropix Integrations API: Link External Systems to an Organization

Create, list, reconnect, and delete Integrations: the Organization’s linked credentials for external systems that feed data into its Entities through Source Feeds and bank feeds. Give each one a purpose, create a Mailbox at the Organization’s email domain, search and read the email of a Gmail, Outlook, or Mailbox account, connect the SII with the company Clave, export the General Ledger to a Google Sheet, connect Xpendit with an API key and read its expenses, connect Rho with an access token and preview its accounts, connect Stripe with read-only access, and store Portal Logins for a bank, Getnet, or Clay, which no Provider reads.

An Integration is a linked external system: the credentials, tokens, and configuration Sintropix stores to reach that system on the Organization’s behalf. Every grant to an external account is an Integration, including the banks and payment providers that feed Bank Accounts. Integrations are the credential side. The feeds are the recurring pull jobs that import data through them. What an Integration can feed depends on its kind:

Kind	Feeds
`sii_mirror`	Up to two Sources, through Source Feeds: one for DTEs (`dte`) and one for boletas de honorarios (`honorarium`)
`bsale`, `wasabil`	A Source, through a Source Feed of DTEs (`dte`)
`fintoc`, `plaid`, `global66`, `cardda`, `dlocal`, `mercadopago`, `polar`, `stripe`	One or more Bank Accounts, through bank feeds
`xpendit`	A Source that holds Expense Renditions for each of its Subsidiaries, through a Source Feed of expenses (`expense`). Each sync lands the expenses Xpendit approved as approved Expense Claims. You can also read its expenses on demand
`mercadolibre`, `buk`, `notion`, `rho`	Nothing yet
`gmail`, `outlook`, `mailbox`	Nothing. You search and read their email on demand instead. See Read email
`google_sheets`	Nothing. It receives the General Ledger instead. See Google Sheets

An Organization can hold more than one Integration at a time (for example, a Bsale document feed alongside a Fintoc bank and a Mercado Pago authorization). Each external account can be connected only once. The fintoc kind connects a bank login through the Fintoc widget. Only staff can connect or reconnect a bank through Fintoc. A client connects a bank by storing its Bank Login. The global66 kind connects Global66 with a client id and a client secret, and discovers every active wallet of that client. The cardda kind connects a Cardda company with its API key, and the dlocal kind connects a dLocal Go merchant with its API key and secret key. Sintropix reads the Provider before it stores the credentials, so credentials that cannot read are refused at connect. The plaid kind connects a US bank through Plaid Link. Plaid Link shows US banks only, in English, and asks for access to the bank’s transactions, with up to 730 days of history. Your bank password goes to Plaid and never reaches Sintropix. It can feed Bank Accounts with the bank’s posted transactions. See POST /integrations/plaid/link-tokens and Bank Feeds. The mercadopago kind connects a Mercado Pago account through OAuth. It can feed a Bank Account with the account’s available money. See Bank Feeds. The gmail and outlook kinds connect an email account: a Gmail account or a Microsoft Outlook account. You connect it from the app. Sintropix only reads: it never sends, changes, or deletes email. An Organization can connect several email accounts, but each account can be connected only once. You can search and read the email of a connected account through the API. The mailbox kind is an email address that Sintropix holds for the Organization, such as [email protected]. You create it in Sintropix: there’s no outside account to connect. An Organization can hold several Mailboxes, all at its own email domain. See Mailbox. The google_sheets kind connects one Google Sheet through Google OAuth. Sintropix writes the General Ledger of the current Fiscal Year of every Entity of the Organization to that Sheet, every four hours and whenever you ask. See Google Sheets. The xpendit kind connects the enterprise of an Xpendit account, the expense tool, with its API key. You can read the expenses and funds of each of its Subsidiaries, and route each Subsidiary to a Source of Expense Renditions. See Xpendit. The stripe kind connects a Stripe account through OAuth, by installing the Sintropix Stripe App in that account with read-only access. It can feed a Bank Account with each currency of the account’s Stripe payments balance. See Stripe and Bank Feeds. The buk kind connects a Buk tenant, the payroll system, with its address and an API key. It feeds nothing yet. You can list the Empresas the key reaches. See Buk. The rho kind connects a business on Rho, the US business banking platform, with a read-only API access token. It feeds nothing yet, but you can preview every account of the business with its current balance, Treasury and rewards accounts included. See Rho. The notion kind connects a Notion workspace through OAuth, with read-only access to the pages and databases you share at consent. It feeds nothing yet, but you can preview each database it reaches. See Notion. The polar kind connects a Polar account through OAuth. You grant Sintropix read-only access to the account’s organizations, orders, payments, refunds, disputes, transactions, and payouts. If you clear the transactions or payouts permission on Polar’s consent screen, Sintropix refuses the connection and stores nothing. Sign in to Polar as a user with the owner, admin, or finance role in the organization: Polar shows an organization’s money to those roles only. It can feed a USD Bank Account with each organization’s Polar balance. Sintropix only reads: it never charges, refunds, or withdraws money. See Bank Feeds. To connect a bank that no Provider reads, such as a credit card Fintoc can’t fetch, store its login as a Bank Login. To connect the Getnet merchant portal, store its login as a Getnet Login. To give Sintropix access to Clay, the Chilean ERP you migrate your books from, store it as a Clay Login. None of these is an Integration kind, but the app lists them with the Integrations. The sii_mirror kind connects the SII, the Chilean tax authority, and is the only SII document Provider. You connect it with the company’s RUT and its SII password (Clave), and the SII checks them at once. It then reads the RCV registers of that RUT from Sintropix’s Chilean SII mirror. The mirror reads the SII registers every 4 hours, so a document reaches it a few hours after the SII records it. See SII. In the app, open Configuración → Integraciones and click Conectar integración. The catalog lists every option with its logo, and you can search it or filter it by tag: Banco, Pagos, Ventas, Facturador, Impuestos, Rendiciones, Correo, ERP, or Remuneraciones. Each Chilean bank is its own option, and you can find it by its short name too, such as “bci”. Pick an option and fill in its form. For a Provider that uses OAuth, such as Google or Mercado Pago, you continue on the Provider’s page and return to Sintropix afterwards. Connecting asks for no Entity. When the connection is stored, its panel opens on the step it still lacks, where you route it to the Entities (Entidades legales) of the Organization. For a document Provider, pick the Source each Document Family lands in, from the Sources of every Entity grouped by Entity, and the date to read from. You can also create a Source in any Entity. For a bank Provider, link each of its accounts to a Bank Account of any Entity, or create one in the Entity you pick. Until you finish that step, the list shows the connection as Falta elegir fuentes or Falta elegir cuentas. The list shows every connection of the Organization. Each Integration’s row names the Entities its feeds reach, or Sin asignar until a feed routes it. A Portal Login’s row names its own Entity.

Open in the app. This resource has a page in the Sintropix web app at https://app.sintropix.com/organizations/{organizationId}/settings/integrations, where each id in braces is the same UUID as in the API route or response. When you mention a record to a user, include that link. See Link to the App for the full URL grammar.

Integrations belong to the Organization

An Integration belongs to the Organization, not to one Entity. Its feeds route it: each Source Feed or bank feed names the Entity whose Source or Bank Account it fills. One Integration can feed several Entities of its Organization. For example, one bank login can feed a Bank Account in each of two Entities. No tax id decides or limits where a feed lands: any feed can land in any Entity of the Organization. The routes follow the same split:

Every Integration route lives under /api/organizations/:organizationId/integrations: connect, list, the Fintoc Link Intent, the Plaid Link token, reconnect, the replacement of an API key, the purpose, the SII legal representative’s Clave, the discovered accounts, the Provider Accounts, the General Ledger Export, a Mailbox and its Conversations, the email of a Gmail, Outlook, or Mailbox account, the expenses of an Xpendit account, the accounts of a Rho business, the preview of a Notion database, and disconnect.
Every feed route lives under the Entity it lands in, /api/entities/:entityId/.... So does the copy of an email attachment into an Entity. They take an Integration of that Entity’s Organization. An Integration of another Organization answers 404 with INTEGRATION_NOT_FOUND_ERROR.

Connecting, reconnecting, disconnecting, and setting the purpose of an Integration need the books write permission in the Organization, which a client or staff caller holds. A viewer can only list Integrations, and can’t read the email of a Gmail, Outlook, or Mailbox account, the expenses of an Xpendit account, or the preview of a Notion database. An API key confined to one Entity:

Lists every Integration of its Organization, but sees only the Sources and Bank Accounts of its own Entity.
Can’t connect, reconnect, renew, or disconnect an Integration, replace its API key, run a General Ledger Export, read or copy the email of a Gmail, Outlook, or Mailbox account, or read the expenses of an Xpendit account or the preview of a Notion database. It gets 403 with PERMISSION_DENIED_ERROR.
Adds and removes only the feeds that land in its own Entity.

An Entity whose feed routes an Integration of its Organization, or whose Book a Google Sheets Integration exports, can’t move to another Organization. See PATCH /api/entities/:entityId/organization.

The Integration object

The access token is stored encrypted and is never returned on any read.

Field	Type	Description
`id`	uuid	Integration id.
`organizationId`	uuid	Owning Organization.
`kind`	`bsale` \| `wasabil` \| `sii_mirror` \| `fintoc` \| `global66` \| `cardda` \| `dlocal` \| `plaid` \| `mercadopago` \| `mercadolibre` \| `gmail` \| `outlook` \| `mailbox` \| `polar` \| `google_sheets` \| `xpendit` \| `stripe` \| `buk` \| `notion` \| `rho`	The external system.
`providerRef`	string \| null	The provider’s own handle for the connected account (for Bsale, the instance number; for `sii_mirror`, the company RUT the SII accepted at connect, unformatted; for `fintoc`, the Fintoc Link; for `plaid`, the Plaid Item id; for Mercado Pago and Mercado Libre, the account ID; for `gmail` and `outlook`, the account’s email address; for `mailbox`, its address; for `polar`, the email address of the Polar user who granted access; for `google_sheets`, the id of the Google Sheet; for `xpendit`, the id of the Xpendit enterprise; for `stripe`, the Stripe account id, such as `acct_1Q2w3E4r5T6y7U8i`; for `buk`, the tenant, the subdomain of its `buk.cl` address; for `notion`, the id of the Notion workspace; for `rho`, the id of the Rho business). `null` when a document provider could not determine it at connect time.
`documentCount`	integer \| null	Number of documents the provider reported when the credential was verified at connect time. Only `bsale` and `wasabil` state it; `null` for every other kind.
`institutionName`	string \| null	The bank’s display name, as the Provider reports it. Only `fintoc` and `plaid` state it; `null` for every other kind.
`holderId`	string \| null	The account holder’s tax id (RUT), unformatted, as the Provider reports it. Only `fintoc` and `cardda` state it; `null` for every other kind.
`mode`	`test` \| `live` \| null	Whether a `fintoc`, `plaid`, or `stripe` Integration runs against the Provider’s test or live environment. `null` for every other kind.
`accountName`	string \| null	For `stripe`, the business name of the Stripe account, or its Dashboard name when it has no business name, as read at connect. It can be `null` for a Stripe account that states neither. For `notion`, the name of the Notion workspace. `null` for every other kind.
`country`	string \| null	For `stripe`, the country of the Stripe account, as an ISO 3166-1 alpha-2 code such as `US`, read at connect. `null` for every other kind.
`defaultCurrency`	string \| null	For `stripe`, the default currency of the Stripe account, as an uppercase ISO 4217 code such as `USD`, read at connect. `null` for every other kind.
`feedableFamilies`	array	The Document Families this Integration’s provider can feed: `["dte", "honorarium"]` for `sii_mirror`, `["dte"]` for `bsale` and `wasabil`, `["expense"]` for `xpendit`. Empty for every kind that feeds no documents.
`sourceFeeds`	array	The Source Feeds that read through this Integration, in the shape documented on Source Feeds. Each Entity holds at most one Feed per family. Empty when the Integration feeds no Source.
`fedBankAccounts`	array	`{ id, name, entityId }` of each Bank Account this Integration feeds, in any Entity, in name order. Empty when it feeds none.
`routedEntities`	array	`{ id, name }` of each Entity the Integration’s feeds reach, in name order. Empty while no feed routes it.
`bookId`	uuid \| null	For `google_sheets`, the Book the export reads for the Entity that keeps it. `null` for every other kind, and when no Book was picked.
`lastGeneralLedgerExport`	object \| null	For `google_sheets`, the last General Ledger Export. `null` until the first export runs, and always `null` for every other kind.
`scopes`	string[]	The permissions the Provider granted. Set for `mercadopago`, `mercadolibre`, `polar`, `google_sheets`, and `stripe`; empty for every other kind.
`tokenExpiresAt`	ISO 8601 timestamp \| null	When the stored access of a `mercadopago`, `mercadolibre`, `polar`, `google_sheets`, or `stripe` Integration expires. `null` for every other kind.
`purpose`	string \| null	What the account is for, in your own words, such as “Facturas de proveedores de Acme”. It helps a person or an agent pick the right account when the Organization holds several. Up to 500 characters. `null` until you set it.
`grantHealth`	`working` \| `failed` \| `unknown` \| null	For `gmail` and `outlook`, whether the account’s access still works, checked on each list. `failed` means the access expired or was revoked: disconnect the Integration and connect the account again. `unknown` means Sintropix couldn’t check it right now. For `mailbox`, `working` when Sintropix reaches its inbox and `unknown` otherwise; a Mailbox holds no access that can expire, so it’s never `failed`. `null` for every other kind.
`createdAt`, `updatedAt`	ISO 8601 timestamp	Row timestamps.

POST `/integrations`

POST /api/organizations/:organizationId/integrations Create an Integration of the Organization by handing Sintropix a provider-issued access token. The token is verified against the provider once, then stored encrypted. Connecting asks for no Entity: route the Integration to Entities afterwards, through its feeds. This route connects the document Providers, the bank Providers, Xpendit, Buk, and Rho. Mercado Pago, Mercado Libre, Gmail, Outlook, Polar, Google Sheets, Stripe, and Notion use OAuth and are connected from Configuración → Integraciones in the Sintropix app. You cannot create them through this endpoint. A Mailbox has its own route: POST /integrations/mailbox. Body. The shape depends on kind. Every kind takes an id:

Field	Type	Required	Description
`id`	uuid	Yes	Client-generated id. Retrying the same `POST` with the same id is rejected instead of creating a duplicate.
`kind`	`bsale` \| `wasabil` \| `xpendit` \| `buk` \| `rho` \| `sii_mirror` \| `fintoc` \| `plaid` \| `global66` \| `cardda` \| `dlocal`	Yes	The external system to link. `mercadopago`, `mercadolibre`, `gmail`, `outlook`, `mailbox`, `polar`, `google_sheets`, `stripe`, and `notion` are not accepted here.

Each kind adds its own fields:

Kind	Fields	Description
`bsale`, `wasabil`, `xpendit`, `rho`	`accessToken` (string)	The provider’s API access token. For `xpendit`, the API key of the enterprise. For `rho`, an API access token of the Rho business. See Create the token in Rho. Whitespace is trimmed and must be non-empty.
`buk`	`tenant` (string), `accessToken` (string)	The address of your Buk, such as `acme.buk.cl` or a full `https://acme.buk.cl/...` address, and its API key. Sintropix keeps only the subdomain, and sends the key only to that `buk.cl` address. An address outside `buk.cl` is refused with `400`. The key must be non-empty after trimming.
`sii_mirror`	`rut` (string), `clave` (string)	The company’s RUT and its SII password (Clave). The RUT takes the same format and check-digit rule as a Portal Login `rut`. The Clave must be non-empty. See SII.
`fintoc`	`exchangeToken` (string)	The token the Fintoc widget mints after you create a link intent and the user completes the widget.
`plaid`	`publicToken` (string)	The public token Plaid Link mints after you create a Link token and the user signs in to the bank. Connecting the same Plaid Item twice is refused with `409`.
`global66`	`clientId` (string), `clientSecret` (string)	Your Global66 client credentials. The Integration discovers every active wallet of that client, so you don’t name the accounts. A client id can be connected only once: connecting it again answers `409` with `INTEGRATION_ACCOUNT_ALREADY_CONNECTED_ERROR`.
`cardda`	`apiKey` (string)	The Cardda API key. It selects the company, and the Integration discovers that company’s one CLP wallet.
`dlocal`	`apiKey` (string), `secretKey` (string)	The dLocal Go API key and its paired secret key. They name the merchant, and the Integration discovers its one balance.

For sii_mirror, the SII checks the RUT and Clave before Sintropix creates the Integration, so the request can take up to about a minute. A Clave the SII refuses answers 422 with SII_CLAVE_REFUSED_ERROR. When the SII gives no answer in time, the request answers 503 with SII_UNAVAILABLE_ERROR and creates nothing. Retry in a few minutes. Credentials the Provider refuses answer 422 with INTEGRATION_CONNECT_REJECTED_ERROR. An API key Xpendit or Buk refuses, or a token Rho refuses, answers 422 with INTEGRATION_PROVIDER_UNAUTHORIZED_ERROR. A Rho token that lacks a scope Sintropix needs answers 422 with INTEGRATION_CONNECT_REJECTED_ERROR. A Buk address that holds no tenant, or a key that reaches no Empresa, answers 422 with INTEGRATION_CONNECT_REJECTED_ERROR. An external account another Integration already holds answers 409 with INTEGRATION_ACCOUNT_ALREADY_CONNECTED_ERROR.

Response (201): the Integration object (its sourceFeeds and fedBankAccounts are empty on creation).

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "d3e4f5a6-b7c8-4d9e-8f0a-1b2c3d4e5f6a",
    "kind": "bsale",
    "accessToken": "b7f3c9e1a2d4f6081e3c5a7b9d1f2e4c"
  }'

{
  "id": "d3e4f5a6-b7c8-4d9e-8f0a-1b2c3d4e5f6a",
  "organizationId": "5f1c2a3b-4d5e-4f6a-8b7c-9d0e1f2a3b4c",
  "kind": "bsale",
  "providerRef": "12345",
  "documentCount": 355,
  "institutionName": null,
  "holderId": null,
  "mode": null,
  "feedableFamilies": ["dte"],
  "sourceFeeds": [],
  "fedBankAccounts": [],
  "routedEntities": [],
  "bookId": null,
  "lastGeneralLedgerExport": null,
  "createdAt": "2025-01-02T12:00:00.000Z",
  "updatedAt": "2025-01-02T12:00:00.000Z"
}

Connect the SII with the company’s RUT and Clave:

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "e7a1b2c3-d4e5-4f6a-8b9c-0d1e2f3a4b5c",
    "kind": "sii_mirror",
    "rut": "76.123.456-0",
    "clave": "my-sii-clave"
  }'

Connect a dLocal Go merchant:

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "0192a8b4-0000-7000-8000-000000000001",
    "kind": "dlocal",
    "apiKey": "dlocal_api_key",
    "secretKey": "dlocal_secret_key"
  }'

After you connect a bank Provider, list its accounts and feed them into Bank Accounts of any Entity. See Bank Feeds. After you connect a document Provider, feed a Source of any Entity with it. See Source Feeds.

POST `/integrations/fintoc/link-intents`

POST /api/organizations/:organizationId/integrations/fintoc/link-intents Start the Fintoc connect flow. Sintropix creates a Link Intent at Fintoc and answers what the frontend needs to open the Fintoc widget. When the user completes the widget, it mints an exchange token. Send that token to POST /integrations with kind: "fintoc". The widget needs a browser, so you can’t complete a Fintoc connect from the API alone.

Only a staff caller can create a Link Intent. Any other caller gets 403 (PERMISSION_DENIED_ERROR). A client connects a bank by storing a Bank Login instead.

Body

Field	Type	Required	Description
`holderType`	`business` \| `individual`	Yes	Who holds the account at the bank.

Response

Field	Type	Description
`widgetToken`	string	Token the Fintoc widget needs.
`publicKey`	string	Public key for the widget session.

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/fintoc/link-intents" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{"holderType":"business"}'

POST `/integrations/plaid/link-tokens`

POST /api/organizations/:organizationId/integrations/plaid/link-tokens Start the Plaid connect flow. Sintropix creates a Link token at Plaid and answers it. Open Plaid Link with it. When the user signs in to the bank, Plaid Link mints a public token. Send that token to POST /integrations with kind: "plaid". Plaid Link needs a browser, so you can’t complete a Plaid connect from the API alone. No request body. Response

Field	Type	Description
`linkToken`	string	Token that opens Plaid Link.

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/plaid/link-tokens" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent"

Then connect with the public token Plaid Link minted:

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "4a5b6c7d-8e9f-4a0b-9c1d-2e3f4a5b6c7d",
    "kind": "plaid",
    "publicToken": "public-production-1a2b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d"
  }'

The response is the Integration object, with the bank’s name in institutionName. Next, list the bank’s accounts and feed them into Bank Accounts.

POST `/integrations/:integrationId/reconnect`

POST /api/organizations/:organizationId/integrations/:integrationId/reconnect Restore a Fintoc Integration whose bank stopped trusting the stored grant. You know it needs this when its discovered accounts answer status: "login_required". Run the Fintoc widget again and send the fresh exchange token. The Integration keeps its id and every feed it holds. Only fintoc Integrations reconnect, and only a staff caller can reconnect one. Any other caller gets 403 (PERMISSION_DENIED_ERROR). To repair a Global66, Cardda, dLocal Go, or Plaid Integration whose credentials stopped working, disconnect it and connect again. For Plaid, this includes a bank login that expired. For Xpendit or Buk, replace its API key instead. Body

Field	Type	Required	Description
`exchangeToken`	string	Yes	Fresh token from the Fintoc widget.

A grant from another bank or another holder, or an Integration that is not fintoc, is refused with 409 and INTEGRATION_GRANT_MISMATCH_ERROR.

Response: the restored Integration object.

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/reconnect" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{"exchangeToken":"ex_tok_456"}'

GET `/integrations`

GET /api/organizations/:organizationId/integrations List every Integration of the Organization, in the order they were connected, including any Mercado Pago, Mercado Libre, Gmail, Outlook, Polar, Google Sheets, Stripe, or Notion authorization connected from the app, and every Mailbox. Each item carries its Source Feeds, the Bank Accounts it feeds, and the Entities its feeds reach. A Google Sheets Integration carries its last General Ledger Export. An API key confined to one Entity gets every Integration of the Organization, with only the Source Feeds and Bank Accounts of its own Entity. routedEntities still names every Entity a feed reaches.

Response: array of Integration objects.

PUT `/integrations/:integrationId/purpose`

PUT /api/organizations/:organizationId/integrations/:integrationId/purpose Set or clear the purpose of an Integration: what the account is for, in your own words. Write it so a colleague or an agent can tell your accounts apart, for example “Casilla de facturas de proveedores” for one Gmail account and “Correo personal de la gerenta” for another. Any kind of Integration takes a purpose. In the app, open the Integration’s panel. Propósito is the first row of its details, and you edit it in place. Body

Field	Type	Required	Description
`purpose`	string \| null	Yes	1 to 500 characters after trimming. `null` clears it. A blank string is refused with `400`. Unknown keys are refused with `400`.

Response: the Integration object, with its new purpose.

curl -X PUT "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/purpose" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "x-audit-reason: Name the supplier invoice mailbox" \
  -H "Content-Type: application/json" \
  -d '{ "purpose": "Casilla de facturas de proveedores" }'

DELETE `/integrations/:integrationId`

DELETE /api/organizations/:organizationId/integrations/:integrationId Remove an Integration. A Mailbox can’t be removed. Every feed of the Integration is removed as part of the same operation, in every Entity: its Source Feeds and the feed of each Bank Account it fed. The Sources, the Bank Accounts, and the documents and Movements already landed stay.

For a fintoc Integration, Sintropix also deletes the Link at Fintoc, so the bank stops being read.
For a plaid Integration, Sintropix first removes the bank login at Plaid. If Plaid already removed it, the disconnect still succeeds. If Plaid fails or can’t be reached, the disconnect answers 424 or 503 and the Integration stays. Retry later.
For a sii_mirror Integration, the SII mirror first deletes the company Clave and the legal representative’s Clave, and stops reading that RUT. If the mirror is busy with that RUT or can’t be reached, the disconnect answers 503 with SII_UNAVAILABLE_ERROR, and the Integration and both Claves stay. Retry in a few minutes.
For a stripe Integration, Sintropix first uninstalls the Sintropix Stripe App from the account. If the account already uninstalled it, the disconnect still succeeds. If Stripe fails, the disconnect answers 424 with INTEGRATION_PROVIDER_FAILURE_ERROR and the Integration stays. Retry later.
For a notion Integration, Sintropix first revokes the grant at Notion. If Notion already removed it, the disconnect still succeeds. If Notion fails, the disconnect answers 424 with INTEGRATION_PROVIDER_FAILURE_ERROR and the Integration stays. Retry later.
A mailbox Integration is refused with 409 (MAILBOX_NOT_REMOVABLE_ERROR), because removing it would delete its email. See A Mailbox stays.
For every other kind, Sintropix removes the stored credentials or authorization only. The grant on the provider’s side is not revoked. For google_sheets, the Sheet keeps the last General Ledger written to it.

Response

Field	Type	Description
`deletedIntegrationId`	uuid	The removed Integration.
`unfedBankAccounts`	array	Every Bank Account that lost its feed, in any Entity, in the shape documented on Bank Accounts without the summary fields, and with `feed` set to `null`. Empty when the Integration fed no Bank Account.

curl -X DELETE "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent"

{
  "deletedIntegrationId": "0192a8b4-0000-7000-8000-000000000001",
  "unfedBankAccounts": []
}

SII

The SII Integration (sii_mirror) reads the company’s DTEs and boletas de honorarios from the SII through Sintropix’s SII mirror. Sintropix stores the company RUT as the Integration’s providerRef, and none of the Clave. The Clave is held by the SII mirror, which signs in to the SII with it.

Connect the SII

In the app, open Configuración → Integraciones, click Conectar integración, and pick SII. Type the company’s RUT and its Clave del SII, then click Conectar. While the SII checks the Clave, the form shows Verificando la Clave con el SII…. A refused Clave shows Clave incorrecta under the field. Through the API, send kind: "sii_mirror" with rut and clave to POST /integrations. The SII checks the Clave before the Integration exists:

Outcome	Answer
The SII accepts the RUT and Clave	`201` with the Integration
The SII refuses the Clave	`422` with `SII_CLAVE_REFUSED_ERROR`. Nothing is stored
The SII gives no answer in time, or the mirror is busy with that RUT	`503` with `SII_UNAVAILABLE_ERROR`. Nothing is stored. Retry in a few minutes
Another Integration already reads that RUT	`409` with `INTEGRATION_ACCOUNT_ALREADY_CONNECTED_ERROR`

The connect asks for no Entity, and the Entity’s tax id doesn’t need to match the RUT. Route the documents with a Source Feed on the Entity they belong to. Each document a feed lands names the connected RUT, with the Entity’s name, as the company’s side: the issuer of a sale and the receiver of a purchase. The app doesn’t offer the SII Login for new connections. SII Logins stored before keep showing in the list.

The legal representative’s Clave

The company Clave reads the RCV registers. The SII opens the PDF and XML of the DTEs only to the legal representative, so add the legal representative’s own RUT and Clave to receive those files. It’s optional: the company Clave alone connects the SII. In the app, open Conectar integración and pick Clave del representante legal, under the Impuestos tag. The option is dimmed until the company’s SII is connected. When the Organization has two or more SII Integrations, the dialog first asks which company, by RUT. The option shows a check once the SII mirror holds a Clave or a certificate of the legal representative of every connected company. Disconnecting the SII deletes the legal representative’s Clave together with the company Clave.

PUT `/integrations/:integrationId/sii-representative-clave`

PUT /api/organizations/:organizationId/integrations/:integrationId/sii-representative-clave Add the legal representative’s Clave to an SII Integration. The SII checks it at once, the same way as the company Clave. Sintropix stores neither the RUT nor the Clave. Sending it again replaces the Clave the SII mirror holds for that person. Body

Field	Type	Required	Description
`rut`	string	Yes	The legal representative’s own RUT, as a person. Same format and check-digit rule as a Portal Login `rut`. The company’s RUT is refused.
`clave`	string	Yes	The legal representative’s SII password (Clave). Must be non-empty.

Response: the Integration object.

Status	Code	When it happens
`422`	`SII_REPRESENTATIVE_RUT_IS_TAXPAYER_RUT_ERROR`	`rut` is the company’s own RUT. Nothing is sent to the SII
`422`	`SII_CLAVE_REFUSED_ERROR`	The SII refused the Clave
`422`	`INTEGRATION_REPRESENTATIVE_CLAVE_NOT_SUPPORTED_ERROR`	The Integration isn’t `sii_mirror`
`503`	`SII_UNAVAILABLE_ERROR`	The SII gave no answer in time. Retry in a few minutes

curl -X PUT "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/sii-representative-clave" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "rut": "12.345.678-5",
    "clave": "representative-sii-clave"
  }'

GET `/integrations/:integrationId/sii-representative-clave`

GET /api/organizations/:organizationId/integrations/:integrationId/sii-representative-clave Read whether the SII mirror holds a Clave or a certificate of the company’s legal representative. Sintropix asks the SII mirror on every read. Response

Field	Type	Description
`representativeClave`	object \| null	`null` while the SII mirror holds no Clave or certificate of the legal representative.
`representativeClave.rut`	string	The legal representative’s RUT.
`representativeClave.verifiedAt`	ISO 8601 timestamp \| null	The last time the SII accepted a sign-in with it. `null` until the first sign-in.

{
  "representativeClave": {
    "rut": "12345678-5",
    "verifiedAt": "2026-10-22T14:00:00.000Z"
  }
}

An Integration that isn’t sii_mirror answers 422 with INTEGRATION_REPRESENTATIVE_CLAVE_NOT_SUPPORTED_ERROR. When the SII mirror refuses the read, it answers 424. When the SII mirror can’t be reached, it answers 503.

Gmail and Outlook

A gmail or outlook Integration connects one email account of the Organization. Sintropix keeps no copy of the account’s email. You search and read it on demand, and you can copy an attachment into an Entity, for example to attach a supplier’s PDF to its Invoice. Sintropix only reads: it never sends, changes, or deletes email.

Connect an email account

You connect an email account from the app, because Google and Microsoft ask for consent in a browser:

Open Configuración → Integraciones, click Conectar integración, and pick Gmail or Outlook, under the Correo tag.
Continue on Composio, which holds the account’s access for Sintropix, and allow access on Google or Microsoft with the account you want to connect.

Google asks for full access to the mailbox, but Sintropix only reads it. Outlook asks for read access to the mail only. For a step-by-step guide written for the account owner, see Connect Gmail.

Mailbox

A mailbox Integration is an email address that Sintropix holds for the Organization, such as [email protected]. Your clients and suppliers send or forward invoices and other documents to it, and you read them in Sintropix. There’s no outside account to connect: Sintropix creates the address and receives its email. Sintropix doesn’t turn that email into documents.

A Conversation is a chain of emails on one subject, like a thread in an email client.
An email is one message in a Conversation, received by the Mailbox or sent from it.

An Organization can hold as many Mailboxes as it needs, for example facturas@ for supplier invoices and rendiciones@ for expense receipts. Give each one a purpose so a colleague or Erwin can tell them apart.

The email domain

Every Mailbox of an Organization takes its address at the Organization’s email domain: a subdomain of sintropix.com that belongs to that Organization alone, such as acme.sintropix.com. Sintropix sets it for you. A Superadmin picks it for the Organization in the staff panel, with PATCH /organizations/:organizationId/email-domain. The Organization’s emailDomain is null until then, and the Organization can’t create a Mailbox. Ask Sintropix to set it. Once a Mailbox lives at the domain, the domain can’t change.

Create a Mailbox

Open Configuración → Integraciones, click Conectar integración, and pick Casilla de correo, under the Correo tag.
Enter the Nombre de la casilla: the part of the address before @.
Click Crear casilla.

The Mailbox’s panel opens with its address, its purpose, and Abrir correo. When the Organization has no email domain yet, the form says Esta empresa aún no tiene dominio de correo. Pídelo a Sintropix. Choose the name carefully: you can’t rename a Mailbox, and you can’t remove it. To have Gmail send your invoices to a Mailbox automatically, see Forward invoices from Gmail.

POST `/integrations/mailbox`

POST /api/organizations/:organizationId/integrations/mailbox Create a Mailbox at the Organization’s email domain. It needs the books write permission in the Organization, which a client or staff caller holds. An API key confined to one Entity gets 403 with PERMISSION_DENIED_ERROR. Body. Unknown keys are refused with 400.

Field	Type	Required	Description
`id`	uuid	Yes	Client-generated id of the new Integration. An id already in use is refused with `409` (`INTEGRATION_ALREADY_EXISTS_ERROR`).
`name`	string	Yes	The part of the address before `@`. Up to 64 characters: lowercase letters and digits, in groups joined by a single `.` or `-`, such as `facturas` or `compras.chile`. Anything else is refused with `400`.

An Organization with no email domain is refused with 409 (MAILBOX_EMAIL_DOMAIN_NOT_SET_ERROR).
An address that already exists is refused with 409 (MAILBOX_ALREADY_EXISTS_ERROR). params.address names it. Choose another name.
An email domain that no longer receives email is refused with 409 (EMAIL_DOMAIN_NOT_OPEN_ERROR). params.emailDomain names it. Ask Sintropix to check it.
When Sintropix already holds every Mailbox its email plan includes, the create is refused with 424 (MAILBOX_LIMIT_REACHED_ERROR). Ask Sintropix to raise the limit.

Response 201: the Integration object, with kind: "mailbox" and the new address as providerRef.

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/mailbox" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "x-audit-reason: Mailbox for Acme's supplier invoices" \
  -H "Content-Type: application/json" \
  -d '{ "id": "5c6d7e8f-9a0b-4c1d-8e2f-3a4b5c6d7e8f", "name": "facturas" }'

Read a Mailbox’s Conversations

In the app, click Abrir correo in the Mailbox’s panel. Its Conversations open newest first. Click one to read its emails and download the attachments of the emails it received.

Open in the app. This resource has a page in the Sintropix web app at https://app.sintropix.com/organizations/{organizationId}/mailboxes/{integrationId}, where each id in braces is the same UUID as in the API route or response. Add ?open={conversationId} to open a Conversation in its side panel. When you mention a record to a user, include that link. See Link to the App for the full URL grammar.

Through the API, list the Conversations and read each one with the two routes below. They answer each email’s HTML and a download link for each received attachment, as an email client shows them. To search a Mailbox, or to read its email as plain text, use the email routes instead. Reading Conversations follows the same rule as reading email: staff and client can, a viewer or an API key confined to one Entity can’t. An Integration of the Organization that isn’t a Mailbox answers 404 (MAILBOX_NOT_FOUND_ERROR).

GET `/integrations/:integrationId/conversations`

GET /api/organizations/:organizationId/integrations/:integrationId/conversations List the Conversations in the Mailbox’s inbox, newest first, 50 per page. Query

Parameter	Type	Required	Description
`after`	uuid	No	The `nextCursor` of the previous page. Omit it for the first page.

Response

Field	Type	Description
`address`	string	The Mailbox’s address.
`conversations`	array	The Conversations on this page, newest first. See below.
`nextCursor`	string \| null	Pass it back as `after` to read the next, older page. `null` on the last page.

Each element of conversations:

Field	Type	Description
`id`	string	Conversation id. Use it with `GET /integrations/:integrationId/conversations/:conversationId`.
`subject`	string \| null	Subject line.
`from`	string \| null	Sender.
`to`	string[]	Recipients.
`emailCount`	integer	Number of emails in the Conversation, at least 1.
`hasAttachment`	boolean	Whether any email in the Conversation has an attachment.
`read`	boolean	Whether the Conversation has been read.
`lastActivityAt`	ISO 8601 timestamp	When the Conversation last received an email.

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/conversations" \
  -H "x-api-key: $SINTROPIX_API_KEY"

{
  "address": "[email protected]",
  "conversations": [
    {
      "id": "4f1c2b7e-9a3d-4e5f-8b6a-0c1d2e3f4a5b",
      "subject": "Factura 45210",
      "from": "[email protected]",
      "to": ["[email protected]"],
      "emailCount": 1,
      "hasAttachment": true,
      "read": false,
      "lastActivityAt": "2026-10-12T13:05:41.000Z"
    }
  ],
  "nextCursor": null
}

GET `/integrations/:integrationId/conversations/:conversationId`

GET /api/organizations/:organizationId/integrations/:integrationId/conversations/:conversationId Read one Conversation with every email in it, oldest first. conversationId must be a UUID. A Conversation that isn’t in the Mailbox answers 404 (CONVERSATION_NOT_FOUND_ERROR). Response

Field	Type	Description
`id`	string	Conversation id.
`subject`	string \| null	Subject line.
`emails`	array	The Conversation’s emails, oldest first. See below.

Each element of emails:

Field	Type	Description
`id`	string	Email id.
`direction`	`inbound` \| `outbound`	`inbound` for an email the Mailbox received, `outbound` for one it sent.
`from`	string	Sender.
`to`	string[]	To recipients.
`cc`	string[]	Cc recipients.
`subject`	string \| null	Subject line.
`text`	string \| null	Plain-text body.
`html`	string \| null	HTML body. Render it in a sandbox: it can load remote images.
`sentAt`	ISO 8601 timestamp	When the email was sent or received.
`attachments`	array	`{ id, filename, size, downloadUrl }` for each attachment. `filename` can be `null`; `size` is in bytes. `downloadUrl` is set only on the attachments of an `inbound` email, and is `null` otherwise. It expires shortly after the read, so read the Conversation again for a fresh link.

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/conversations/$CONVERSATION_ID" \
  -H "x-api-key: $SINTROPIX_API_KEY"

A Mailbox stays

You can’t disconnect a Mailbox, because removing it would delete its email. DELETE /integrations/:integrationId on a Mailbox answers 409 (MAILBOX_NOT_REMOVABLE_ERROR), and the app shows no disconnect option in its panel. As a result, an Organization that holds a Mailbox can’t be deleted.

Mailbox errors

Status	Code	When it happens
`403`	`PERMISSION_DENIED_ERROR`	A `viewer` reads Conversations, or an API key confined to one Entity creates a Mailbox or reads its Conversations
`404`	`MAILBOX_NOT_FOUND_ERROR`	The Organization holds no Mailbox with this id. `params.integrationId`
`404`	`CONVERSATION_NOT_FOUND_ERROR`	The Mailbox holds no Conversation with this id. `params.conversationId`
`409`	`INTEGRATION_ALREADY_EXISTS_ERROR`	The `id` of the new Mailbox is already in use
`409`	`MAILBOX_EMAIL_DOMAIN_NOT_SET_ERROR`	The Organization has no email domain yet. Ask Sintropix to set it. `params.organizationId`
`409`	`MAILBOX_ALREADY_EXISTS_ERROR`	The address already exists. `params.address`
`409`	`MAILBOX_NOT_REMOVABLE_ERROR`	A disconnect names a Mailbox. `params.integrationId`
`409`	`EMAIL_DOMAIN_NOT_OPEN_ERROR`	The Organization’s email domain no longer receives email. `params.emailDomain`
`424`	`MAILBOX_LIMIT_REACHED_ERROR`	Sintropix holds every Mailbox its email plan includes. Ask Sintropix to raise the limit
`503`	`MAILBOX_UNAVAILABLE_ERROR`	The Mailbox can’t be created or read right now. Retry later

Read email

You read the email of a gmail, outlook, or mailbox Integration with the same routes: search it, read an email or its whole Conversation as plain text, and copy an attachment into an Entity. Erwin can read all of them too, so you can ask him to find a supplier’s invoice in any of the Organization’s email accounts. He also searches them on his own as evidence when he reviews a record or leaves a Follow-up, and their purpose tells him which account to look in. See Erwin. A Mailbox reads with a few differences, listed in Read a Mailbox’s email.

Who can read email

Reading the email of the Organization’s accounts is more than reading its books, so it has its own rule:

Caller	Search and read email	Copy an attachment into an Entity
`staff` or `client`	Yes	Yes
`viewer`	No	No
An API key confined to one Entity	No	No

A refused caller gets 403 with PERMISSION_DENIED_ERROR. Sintropix logs each email whose content it hands out and each attachment it copies, under the request’s Audit Envelope. A search isn’t logged, because it returns only headers and a short snippet. Reading an email with an API key needs x-audit-actor and x-audit-reason, as a write does.

The Email object

Field	Type	Description
`id`	string	The email’s id at Google or Microsoft, or a Mailbox email’s id. Use it to read the email or copy an attachment.
`conversationId`	string	The id of the email’s Conversation: the thread it belongs to.
`receivedAt`	ISO 8601 timestamp	When the email arrived.
`from`	object \| null	`{ name, address }` of the sender. `name` can be `null`.
`to`, `cc`	array	`{ name, address }` of each recipient.
`subject`	string	The subject.
`attachments`	array	`{ id, filename, contentType, byteSize }` of each attachment. Use `id` to copy it.
`snippet`	string	On a search only: the first words of the body.
`body`	string	On a read only: the body as plain text. HTML is removed. A body over 20,000 characters is cut and ends with `[The body goes on; it was cut here.]`.

GET `/integrations/:integrationId/emails`

GET /api/organizations/:organizationId/integrations/:integrationId/emails Search the email of a Gmail, Outlook, or Mailbox account, newest first. The search covers received and sent email. It leaves out drafts, spam, and deleted email. Query parameters. Send at least one criterion. The criteria combine with AND, and each text criterion matches whole words, as the mailbox’s own search does. Sintropix keeps only the letters, digits, and @._- of each term, so a term can’t carry Gmail or Outlook search syntax.

Parameter	Type	Required	Description
`from`	string	No	Words of the sender’s name or address. 1 to 200 characters.
`to`	string	No	Words of a recipient’s name or address, in To or Cc. 1 to 200 characters.
`subject`	string	No	Words of the subject. 1 to 200 characters.
`text`	string	No	Words anywhere in the subject or body. 1 to 200 characters.
`after`	date (`YYYY-MM-DD`)	No	Only email received on or after this day, in Santiago (Chile) time.
`before`	date (`YYYY-MM-DD`)	No	Only email received before this day, in Santiago (Chile) time. Must be later than `after`.
`hasAttachment`	boolean	No	`true` for only email with attachments, `false` for only email without.
`attachmentType`	`pdf` \| `xml` \| `image` \| `spreadsheet` \| `any`	No	Only email with an attachment of this type. Can’t be combined with `hasAttachment=false`.
`limit`	integer	No	Page size, 1 to 50. Default `10`. A Mailbox page holds at most 10.
`cursor`	string	No	The `nextCursor` of the previous page. Send the same criteria with it.

A search with no criterion, an after that isn’t before before, or an attachmentType with hasAttachment=false answers 400. Response

Field	Type	Description
`emails`	array	Email objects with `snippet` and no `body`, newest first.
`nextCursor`	string \| null	Pass it as `cursor` for the next, older page. `null` on the last page. A page can hold fewer emails than `limit` and still have a next page.

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/emails?from=proveedora&attachmentType=pdf&after=2026-10-01" \
  -H "x-api-key: $SINTROPIX_API_KEY"

{
  "emails": [
    {
      "id": "18f2a7c3d4e5b6a1",
      "conversationId": "18f2a7c3d4e5b6a1",
      "receivedAt": "2026-10-21T13:04:00.000Z",
      "from": { "name": "Proveedora Andina SpA", "address": "[email protected]" },
      "to": [{ "name": null, "address": "[email protected]" }],
      "cc": [],
      "subject": "Factura 10452",
      "attachments": [
        { "id": "1.2", "filename": "factura-10452.pdf", "contentType": "application/pdf", "byteSize": 84211 }
      ],
      "snippet": "Adjuntamos la factura 10452 por el despacho de octubre."
    }
  ],
  "nextCursor": null
}

GET `/integrations/:integrationId/emails/:emailId`

GET /api/organizations/:organizationId/integrations/:integrationId/emails/:emailId Read one email as plain text, or its whole Conversation. Query parameters

Parameter	Type	Required	Description
`conversation`	boolean	No	`true` to read every email of the email’s Conversation. Default `false`.

Response: { "emails": [...] }, Email objects with body and no snippet, oldest first. Without conversation, it holds the one email.

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/emails/$EMAIL_ID?conversation=true" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "x-audit-reason: Read the supplier's reply about invoice 10452"

An email the account doesn’t hold answers 404 with INTEGRATION_EMAIL_NOT_FOUND_ERROR.

POST `/api/entities/:entityId/email-attachments`

Copy one attachment of an email into an Entity, then attach it to a record of that Entity. The copy lands where an upload lands before it is confirmed:

Copy the attachment with this route. It answers an attachmentId.
Attach it to an Invoice, a Bank Movement, or a Ledger Entry of the same Entity with that host’s confirm route, sending attachmentId and filename.

The route lives under the Entity because it writes to that Entity, so it needs the books write permission as well as the right to read email. The Integration must belong to the Entity’s Organization. Body

Field	Type	Required	Description
`integrationId`	uuid	Yes	The Gmail, Outlook, or Mailbox Integration.
`emailId`	string	Yes	The `id` of the email.
`attachmentId`	string	Yes	The `id` of the attachment, from the email’s `attachments`.

The file must be one of the accepted content types, up to 25 MB. When the email sends it as a generic binary file, Sintropix takes its type from the file name’s extension, such as .pdf or .xml. Response (201)

Field	Type	Description
`attachmentId`	uuid	Pass it to the confirm route of the record.
`filename`	string	The attachment’s file name. Pass it to the confirm route too.
`contentType`	string	The stored content type.
`byteSize`	integer	The file size in bytes.
`url`	string	A link that opens the copy for a few minutes.

curl -X POST "https://api.sintropix.com/api/entities/$ENTITY_ID/email-attachments" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "x-audit-reason: Attach the supplier's PDF to invoice 10452" \
  -H "Content-Type: application/json" \
  -d '{
    "integrationId": "1b2c3d4e-5f6a-4b7c-8d9e-0f1a2b3c4d5e",
    "emailId": "18f2a7c3d4e5b6a1",
    "attachmentId": "1.2"
  }'

An attachment the email doesn’t hold answers 404 with INTEGRATION_EMAIL_ATTACHMENT_NOT_FOUND_ERROR.

Read a Mailbox’s email

The routes above read a Mailbox with the same contract, with these differences:

Ids. A Mailbox email’s id joins two UUIDs with +, such as 4f1c2b7e-9a3d-4e5f-8b6a-0c1d2e3f4a5b+9b8a7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d. Use it as you receive it. Its conversationId is the id the Conversation routes take.
Page size. A search page holds at most 10 emails. A larger limit still reads 10. Each Conversation appears at most once on a page: the email of it that matched.
What a search covers. Received, archived, and sent email. Spam and deleted email are left out. A new email can take about a minute to show up in a search. When more than 10,000 Conversations match, the search covers the 10,000 with the newest match, so narrow the criteria.
Recipients. The to of a received email lists the addresses the email was delivered to, not its full To line.
Attachment types. contentType comes from the file name’s extension. It’s empty when Sintropix doesn’t accept that type.
Copy. Only the attachments of a received email can be copied. An attachment of an email the Mailbox sent answers 404 (INTEGRATION_EMAIL_ATTACHMENT_NOT_FOUND_ERROR).
Refusals. A Mailbox holds no access that can expire, so it never answers INTEGRATION_GRANT_FAILED_ERROR. When the Mailbox can’t be read, the routes answer 424 (INTEGRATION_PROVIDER_FAILURE_ERROR) or 503 (INTEGRATION_PROVIDER_UNREACHABLE_ERROR or INTEGRATION_NOT_CONFIGURED_ERROR). Retry later.

Email errors

Status	Code	When it happens
`403`	`PERMISSION_DENIED_ERROR`	A `viewer`, or an API key confined to one Entity, reads or copies email
`404`	`INTEGRATION_NOT_FOUND_ERROR`	The Integration doesn’t exist in the Organization, or, on a copy, in the Entity’s Organization
`404`	`INTEGRATION_EMAIL_NOT_FOUND_ERROR`	The account holds no email with that id. `params.integrationId` and `params.emailId`
`404`	`INTEGRATION_EMAIL_ATTACHMENT_NOT_FOUND_ERROR`	The email holds no attachment with that id. `params.integrationId`, `params.emailId`, and `params.attachmentId`
`422`	`INTEGRATION_EMAIL_NOT_SUPPORTED_ERROR`	The Integration isn’t `gmail`, `outlook`, or `mailbox`. `params.kind` names its kind
`424`	`INTEGRATION_GRANT_FAILED_ERROR`	The account’s access expired or was revoked, as `grantHealth: "failed"` shows in the list. Disconnect the Integration and connect the account again
`424`	`INTEGRATION_PROVIDER_FAILURE_ERROR`	Google or Microsoft refused the request, or the Mailbox can’t be read right now
`503`	`INTEGRATION_PROVIDER_UNREACHABLE_ERROR`	Google, Microsoft, or the Mailbox can’t be reached. Retry later
`503`	`INTEGRATION_NOT_CONFIGURED_ERROR`	Sintropix can’t read Mailboxes right now. Retry later

Google Sheets

A Google Sheets Integration keeps a copy of the Organization’s General Ledger in a Google Sheet you own, with every Entity of the Organization in the same tabs. Use it to work on the ledger with Sheets formulas, or to share it with someone who has no access to Sintropix. Sintropix only writes: nothing you change in the Sheet reaches the books. Each Integration exports to one Sheet, and each Sheet can be connected only once. One Google account can connect Sheets for several Organizations.

A client or staff caller can connect a Google Sheet and run an export. An API key confined to one Entity can’t run an export, because it writes every Entity of the Organization. See Access and roles.

Connect a Google Sheet

You connect Google Sheets from the app, because Google asks for consent in a browser:

Open Configuración → Integraciones, click Conectar integración, and pick Google Sheets.
Paste the address of the Sheet, as your browser shows it with the Sheet open. It starts with https://docs.google.com/spreadsheets/d/.
If an Entity of the Organization keeps Books, pick the Libro the export reads for that Entity.
Continue on Google with an account that can edit the Sheet, and keep the permission to edit your spreadsheets checked.

When you return, Sintropix checks that the account can edit the Sheet by creating its tab, and connects the Integration. It refuses the connection, and stores nothing, when:

The address isn’t the address of a Google Sheet.
Google can’t find the Sheet with the account you authorized.
The account can view the Sheet but can’t edit it. Share the Sheet with that account as an editor, then connect it again.
Another Integration already exports to that Sheet.

What the Sheet holds

Each export rewrites three tabs whole: Libro mayor, Plan de cuentas, and Dimensiones. Sintropix finds each tab by its title, creates a missing one, and leaves the rest of the Sheet alone. If you rename or delete a tab, the next export creates a new one with that title. Every Entity of the Organization goes into the same tabs, one Entity after another, in name order. Each Entity’s rows are in that Entity’s own currency. The export reads the Book you picked for the Entity that keeps it. It reads every other Entity with no Book. If another Entity of the Organization keeps Books, the export fails with 400 and BOOK_REQUIRED_ERROR, and params.entityId names that Entity. That export records no run.

Libro mayor

Libro mayor holds the General Ledger of each Entity’s current Fiscal Year, on the calendar of Santiago (Chile). It reads the live Ledger Entries (active and reversed), the same lines as the general ledger report. Each Entity’s rows have one row per line, sorted by account code, then by date:

Column	Content
Entidad	The Entity’s name
Fecha	The entry date, as a Sheets date
Asiento	The Ledger Entry, linked to the entry in the app
Fecha de creación	When the entry was written, as a Sheets date and time in Santiago (Chile)
Código	The Ledger Account code
Cuenta	The Ledger Account name
Glosa	The entry memo
Contacto	The Partner on the line
RUT	The Partner’s tax id
País	The Partner’s country, as an ISO 3166-1 alpha-2 code
Tipo de contacto	`Proveedor`, `Cliente`, or `Ambos`: what the row’s Entity’s books say the Partner is to it. Empty when they say neither
One column per Dimension	The name of the Dimension Value the line carries for that Dimension, or empty. Every Dimension of the Organization takes a column, in name order, even one no line uses
Moneda	The Entity’s currency, which Débito, Crédito, and Saldo are in
Débito	The debit amount
Crédito	The credit amount
Saldo	The account’s running balance after this line, signed by the account’s normal side
Moneda transacción	The line’s transaction currency. The Entity’s currency for a line booked in it
Monto transacción	The line’s amount in its transaction currency
Tipo de cambio	The line’s exchange rate. `1` for a line booked in the Entity’s currency

Amounts and rates are numbers in currency units, not minor units, so Sheets formulas work on them. Each account of each Entity opens with a Saldo inicial row dated the first day of the Entity’s Fiscal Year. It holds what the account carries into the Fiscal Year, in Saldo and as its own transaction at a rate of 1: 0 on an income or expense account, the result of the closed years on the retained earnings account, and the balance before the year on any other account. It has no entry, creation date, Partner, Dimension Value, debit, or credit. An account with no line this Fiscal Year shows that row alone when its balance isn’t zero, and doesn’t show at all when its balance is zero.

Plan de cuentas

Plan de cuentas holds one row per Ledger Account of each Entity, sorted by code:

Column	Content
Entidad	The Entity’s name
Código	The account code
Nombre	The account name
Tipo	The account type, in Spanish: `Activo`, `Pasivo`, `Patrimonio`, `Ingreso`, `Costo de ventas`, `Gasto operacional`, `Otros ingresos`, or `Otros gastos`
Grupo	The account’s own group, as its code prefix and its name
Descripción	The account description

Dimensiones

Dimensiones holds one row per Dimension Value of the Organization, sorted by Dimension name, then by code. A Dimension with no value has no row.

Column	Content
Dimensión	The Dimension’s name
Código	The value’s code
Valor	The value’s name
Código padre	The code of the value’s parent, or empty

Because every export rewrites the whole tabs, running it again is safe: an entry posted, changed, or reversed since the last export shows up on the next one.

When the export runs

Sintropix exports every Google Sheets Integration every four hours. To export right away, click Sincronizar ahora on the Integration’s panel, or call POST /integrations/:integrationId/general-ledger-exports. The panel shows when the last export ran and how many lines it wrote, or why it failed.

The General Ledger Export object

A General Ledger Export is one run that writes the General Ledger of every Entity of the Organization to the Sheet. It states either the lines it wrote or why it wrote nothing: exactly one of lineCount and failure is set.

Field	Type	Description
`id`	uuid	Export id.
`organizationId`	uuid	Owning Organization.
`integrationId`	uuid	The Google Sheets Integration.
`occurredAt`	ISO 8601 timestamp	When the export ran.
`lineCount`	integer \| null	Ledger lines written to Libro mayor, across every Entity. The Saldo inicial rows don’t count. `null` when the export failed.
`failure`	string \| null	Why Google refused the export (see below). `null` when the export succeeded.

`failure`	Meaning	What to do
`authorization_expired`	The Google authorization expired or was revoked	Renew the authorization, or disconnect the Integration and connect the Sheet again
`sheet_not_found`	Google can’t find the Sheet: it was deleted, or the account lost access	Check the Sheet, then connect it again
`sheet_not_writable`	The account can no longer edit the Sheet	Give the account edit access, then export again
`provider_unreachable`	Google couldn’t be reached	Export again in a few minutes
`provider_failure`	Google failed	Export again in a few minutes

POST `/integrations/:integrationId/general-ledger-exports`

POST /api/organizations/:organizationId/integrations/:integrationId/general-ledger-exports Export the General Ledger of every Entity of the Organization to the Integration’s Sheet now. No request body. The export answers 200 with the General Ledger Export it recorded, whether it succeeded or Google refused it. Check failure to tell them apart. An Integration that isn’t google_sheets answers 422 with GENERAL_LEDGER_EXPORT_NOT_SUPPORTED_ERROR. While another export of the same Integration is still writing, including the scheduled one, the request answers 409 with GENERAL_LEDGER_EXPORT_RUNNING_ERROR. Retry when it finishes. When an Entity other than the one of the picked Book keeps Books, the request answers 400 with BOOK_REQUIRED_ERROR and records no run.

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/general-ledger-exports" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent"

{
  "id": "9a0b1c2d-3e4f-4a5b-8c6d-7e8f9a0b1c2d",
  "organizationId": "5f1c2a3b-4d5e-4f6a-8b7c-9d0e1f2a3b4c",
  "integrationId": "1b2c3d4e-5f6a-4b7c-8d9e-0f1a2b3c4d5e",
  "occurredAt": "2026-10-19T15:00:00.000Z",
  "lineCount": 1284,
  "failure": null
}

A refused export:

{
  "id": "0b1c2d3e-4f5a-4b6c-9d7e-8f9a0b1c2d3e",
  "organizationId": "5f1c2a3b-4d5e-4f6a-8b7c-9d0e1f2a3b4c",
  "integrationId": "1b2c3d4e-5f6a-4b7c-8d9e-0f1a2b3c4d5e",
  "occurredAt": "2026-10-19T19:15:00.000Z",
  "lineCount": null,
  "failure": "sheet_not_writable"
}

Xpendit

An xpendit Integration connects one Xpendit enterprise with its API key. Sintropix reads Xpendit and never writes to it. An enterprise holds one or more Subsidiaries, Xpendit’s word for the accounts its expenses and funds belong to. Sintropix calls each one a Provider Account. With an Xpendit Integration you can:

Read what Xpendit holds: each Subsidiary’s recent expenses and its open funds.
Route each Subsidiary to a Source of Expense Renditions of an Entity, with an expense Feed. Each sync lands the expenses Xpendit approved as approved Expense Claims, booked as Expense Renditions with their receipts attached.

Connect Xpendit

In the app, open Configuración → Integraciones, click Conectar integración, and pick Xpendit, under the Rendiciones tag. Paste the API key of your Xpendit enterprise. Through the API, send it to POST /integrations with kind: "xpendit" and accessToken. Sintropix checks the key with Xpendit before it stores it:

Outcome	Answer
Xpendit accepts the key	`201` with the Integration. `providerRef` is the id of the enterprise
Xpendit refuses the key	`422` with `INTEGRATION_PROVIDER_UNAUTHORIZED_ERROR`. Nothing is stored
Another Integration already connects that enterprise	`409` with `INTEGRATION_ACCOUNT_ALREADY_CONNECTED_ERROR`. `params.providerRef` names the enterprise

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "x-audit-reason: Connect the Xpendit enterprise to read its expenses" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "7c8d9e0f-1a2b-4c3d-8e4f-5a6b7c8d9e0f",
    "kind": "xpendit",
    "accessToken": "xpendit-api-key"
  }'

PUT `/integrations/:integrationId/access-token`

PUT /api/organizations/:organizationId/integrations/:integrationId/access-token Replace the API key of an Xpendit, Buk, or Rho Integration, for example after you rotate the key. For Xpendit, the new key must open the same enterprise. For Buk, Sintropix checks the new key at the same tenant. For Rho, the new token must open the same business. The Integration keeps its id and its Feeds. In the app, open the Integration’s panel and click Reemplazar clave de API. Body

Field	Type	Required	Description
`accessToken`	string	Yes	The new API key. Whitespace is trimmed and must be non-empty. Unknown keys are refused with `400`.

Sintropix checks the new key with the Provider first. If it fails any check, the stored key stays:

Status	Code	When it happens
`409`	`INTEGRATION_GRANT_MISMATCH_ERROR`	The key opens another Xpendit enterprise or another Rho business. `params.integrationId`
`422`	`INTEGRATION_PROVIDER_UNAUTHORIZED_ERROR`	Xpendit, Buk, or Rho refuses the key
`422`	`INTEGRATION_CONNECT_REJECTED_ERROR`	The Rho token lacks a scope Sintropix needs
`422`	`INTEGRATION_TOKEN_REPLACEMENT_NOT_SUPPORTED_ERROR`	The Integration isn’t `xpendit`, `buk`, or `rho`. `params.integrationId` and `params.kind`

Response (200): the Integration object.

curl -X PUT "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/access-token" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "x-audit-reason: Rotate the Xpendit API key" \
  -H "Content-Type: application/json" \
  -d '{ "accessToken": "new-xpendit-api-key" }'

Read what Xpendit holds

GET `/integrations/:integrationId/xpendit-overview`

GET /api/organizations/:organizationId/integrations/:integrationId/xpendit-overview Read, for every Subsidiary of the enterprise, the expenses created in the last 30 days and the funds that still hold money. Sintropix reads Xpendit live on every request and stores nothing, so the answer can take several seconds for a large enterprise. In the app, open the Integration’s panel and click Ver gastos to open Gastos en Xpendit. A staff or client caller can read it. A viewer and an API key confined to one Entity get 403 with PERMISSION_DENIED_ERROR. Response

Field	Type	Description
`windowStart`	date (`YYYY-MM-DD`)	30 days before `windowEnd`.
`windowEnd`	date (`YYYY-MM-DD`)	Today, in Santiago (Chile) time.
`subsidiaries`	array	One object per Subsidiary. See below.

Each Subsidiary:

Field	Type	Description
`subsidiaryId`	string	The Subsidiary’s id at Xpendit.
`name`	string	The Subsidiary’s name.
`expenses`	array	Every expense created in the Subsidiary during the window, newest first. See below.
`expenseCountsByType`	object	The number of those expenses for each expense type. Every type is present, with `0` when there are none.
`expenseCountsByState`	object	The number of those expenses for each state. Every state is present.
`unsettledFunds`	array	The funds that are `open` or `pending_settlement`. See below.
`fundCountsByStatus`	object	The number of the Subsidiary’s funds for each fund status, whatever their status.

Each expense:

Field	Type	Description
`expenseId`	string	The expense’s id at Xpendit.
`expenseNumber`	integer \| null	The expense’s number at Xpendit.
`date`	date (`YYYY-MM-DD`)	The date of the expense.
`personName`	string \| null	The person who reported it.
`merchantName`	string \| null	The business that issued the receipt.
`amount`	number	The amount, in units of `currency` as Xpendit states it, not in minor units.
`currency`	string	The currency code, such as `CLP` or `MXN`.
`expenseType`	`reimbursement` \| `corporate_card` \| `recurrent_fund` \| `one_time_fund` \| `other`	How the expense was paid.
`state`	`draft` \| `pending` \| `rejected` \| `approved` \| `accounted` \| `paid`	Where the expense is in Xpendit.
`categoryName`	string \| null	The expense’s category in Xpendit.

Each fund:

Field	Type	Description
`fundId`	string	The fund’s id at Xpendit.
`fundNumber`	integer	The fund’s number at Xpendit.
`description`	string \| null	What the fund is for.
`status`	`pending_approval` \| `pending` \| `open` \| `closed` \| `pending_settlement` \| `settled` \| `rejected`	The fund’s status.
`personName`	string \| null	The person who answers for the fund.
`currency`	string \| null	The fund’s currency code.
`currentAmount`	number \| null	The money the fund holds now, in units of `currency`.

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/xpendit-overview" \
  -H "x-api-key: $SINTROPIX_API_KEY"

{
  "windowStart": "2026-09-26",
  "windowEnd": "2026-10-26",
  "subsidiaries": [
    {
      "subsidiaryId": "4821",
      "name": "Acme Chile",
      "expenses": [
        {
          "expenseId": "90311",
          "expenseNumber": 101,
          "date": "2026-10-25",
          "personName": "Ana Rojas",
          "merchantName": "COPEC",
          "amount": 48180,
          "currency": "CLP",
          "expenseType": "reimbursement",
          "state": "paid",
          "categoryName": "Movilización"
        }
      ],
      "expenseCountsByType": { "reimbursement": 1, "corporate_card": 0, "recurrent_fund": 0, "one_time_fund": 0, "other": 0 },
      "expenseCountsByState": { "draft": 0, "pending": 0, "rejected": 0, "approved": 0, "accounted": 0, "paid": 1 },
      "unsettledFunds": [
        {
          "fundId": "7702",
          "fundNumber": 416,
          "description": "Viaje a Concepción",
          "status": "pending_settlement",
          "personName": "Ana Rojas",
          "currency": "CLP",
          "currentAmount": 14759
        }
      ],
      "fundCountsByStatus": { "pending_approval": 0, "pending": 0, "open": 0, "closed": 0, "pending_settlement": 1, "settled": 3, "rejected": 0 }
    }
  ]
}

A key that Xpendit no longer accepts answers 422 with INTEGRATION_PROVIDER_UNAUTHORIZED_ERROR: replace the key. An Integration that isn’t xpendit answers 422 with INTEGRATION_EXPENSES_NOT_SUPPORTED_ERROR, with params.integrationId and params.kind.

GET `/integrations/:integrationId/provider-accounts`

GET /api/organizations/:organizationId/integrations/:integrationId/provider-accounts List the Provider Accounts of an Integration: for Xpendit, the Subsidiaries of the enterprise; for Buk, the Empresas the key reaches; for Notion, the databases the grant reaches. Sintropix reads them from the Provider on every request. Use an id as the providerAccountId of an expense Feed. Any member of the Organization can list them. Response: an array of { id, name, taxId }, where id is the account’s id at the Provider, as a string. taxId is the RUT of a Buk Empresa, as Buk states it, and null for Xpendit and Notion. An Integration that has no Provider Accounts to list answers 422 with INTEGRATION_EXPENSES_NOT_SUPPORTED_ERROR.

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/provider-accounts" \
  -H "x-api-key: $SINTROPIX_API_KEY"

[
  { "id": "4821", "name": "Acme Chile", "taxId": null },
  { "id": "4822", "name": "Acme México", "taxId": null }
]

Disconnect Xpendit

DELETE /integrations/:integrationId removes the stored key and every expense Feed of the Integration. The Sources stay. Xpendit holds nothing of Sintropix to revoke.

Buk

A buk Integration connects one Buk tenant, the payroll and HR system, with an API key. Sintropix only reads Buk. The Integration lists the Empresas the key reaches, each with its RUT, and feeds nothing yet.

Connect Buk

A Buk administrator creates the key in Buk, under Configuración → Accesos API. Give it read-only access, with the employee and accounting permissions and access to sensitive data, and pick the Empresas Sintropix keeps the books of. In the app, open Configuración → Integraciones, click Conectar integración, and pick Buk, under the Remuneraciones tag. Type the address of your Buk in Dirección de Buk, such as tuempresa.buk.cl, paste the key in Clave de API, and connect. The Integration’s panel then lists the Empresas the key reaches under Empresas en Buk, each with its RUT. Through the API, send POST /integrations with kind: "buk", tenant, and accessToken. When Buk has no tenant at that address, or the key reaches no Empresa, the app says Buk no tiene esa dirección, o la clave no llega a ninguna empresa. Check the address and the Empresas of the key in Buk. To rotate the key, create a new one in Buk and replace it, then delete the old key in Buk.

Disconnect Buk

DELETE /integrations/:integrationId, or disconnecting from the Integration’s panel, removes the key Sintropix stores. Buk keeps the key working until you delete it there too, under Configuración → Accesos API.

Rho

A rho Integration connects one business on Rho, the US business banking platform, with a read-only API access token. Sintropix only reads Rho: it never moves money. You can preview every account of the business with its current balance, including Treasury and rewards accounts. The Integration feeds no Bank Account yet.

Create the token in Rho

Only an Owner or Admin of the Rho business can create an API access token, and Rho asks for a two-factor code to do it.

In Rho, open Settings → API → Access Tokens and click Create token.
Name it for Sintropix, and use the token for Sintropix only.
Pick these scopes, all read-only: accounts:read, transactions:read, statements:read, and businesses:read. Don’t pick any :write scope: Sintropix only reads.
Pick when it expires. Rho allows one year at most, and also expires a token that goes unused for 45 days. Note the date: you replace the token before then.
Leave the list of allowed IP addresses empty.
Confirm with your two-factor code and copy the token. Rho shows it only once.

Connect Rho

In the app, open Configuración → Integraciones, click Conectar integración, and pick Rho, under the Banco tag. Paste the token in Clave de API and connect. Through the API, send POST /integrations with kind: "rho" and accessToken. Sintropix checks the token with Rho before it stores it: it reads the business and every one of its accounts. The token is stored encrypted.

Outcome	Answer
Rho accepts the token	`201` with the Integration. `providerRef` is the id of the Rho business
Rho refuses the token, for example because it expired or was revoked	`422` with `INTEGRATION_PROVIDER_UNAUTHORIZED_ERROR`. Nothing is stored
The token lacks `businesses:read` or `accounts:read`	`422` with `INTEGRATION_CONNECT_REJECTED_ERROR`. Nothing is stored. The app says Rho aceptó el token, pero no deja leer las cuentas.
Another Integration already connects that business	`409` with `INTEGRATION_ACCOUNT_ALREADY_CONNECTED_ERROR`. `params.providerRef` names the business

Each Rho business can be connected only once.

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "x-audit-reason: Connect the Rho business to see its accounts" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "3b4c5d6e-7f80-4a91-b2c3-d4e5f6a7b8c9",
    "kind": "rho",
    "accessToken": "rhobat_your_token"
  }'

When the connection is stored, the Integration’s panel lists the business’s accounts under Cuentas en Rho.

GET `/integrations/:integrationId/rho-overview`

GET /api/organizations/:organizationId/integrations/:integrationId/rho-overview Read the Rho business’s name and every one of its accounts, each with its current balance. Sintropix reads Rho live on every request and stores nothing. In the app, the Integration’s panel shows the same accounts under Cuentas en Rho, each with its name, type, last 4 digits, currency, and balance. Any member of the Organization can read it, a viewer included. Response

Field	Type	Description
`businessName`	string	The legal name of the Rho business.
`accounts`	array	Every account of the business, Treasury and rewards accounts included. See below.

Each account:

Field	Type	Description
`id`	string	The account’s id at Rho.
`name`	string \| null	The account’s name at Rho.
`type`	string	The account’s type, as Rho states it: `checking`, `savings`, `credit`, `investment` (Treasury), or `rewards`. Rho can add a type, so treat any other value as a type you don’t know yet.
`accountNumberLast4`	string \| null	The last 4 digits of the account number.
`balance.amount`	integer	The current balance, in minor units of `balance.currency`. For example, `1250000` in `USD` is $12,500.00.
`balance.currency`	string	The balance’s currency code, such as `USD`.

The balance is the current balance, which reflects the latest posted activity. Rho serves no available balance, so the preview has none.

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/rho-overview" \
  -H "x-api-key: $SINTROPIX_API_KEY"

{
  "businessName": "Acme Inc.",
  "accounts": [
    {
      "id": "acct_0001",
      "name": "Operating",
      "type": "checking",
      "accountNumberLast4": "4821",
      "balance": { "amount": 1250000, "currency": "USD" }
    },
    {
      "id": "acct_0002",
      "name": "Treasury",
      "type": "investment",
      "accountNumberLast4": null,
      "balance": { "amount": 50000000, "currency": "USD" }
    }
  ]
}

Status	Code	When it happens
`404`	`INTEGRATION_NOT_FOUND_ERROR`	The Integration isn’t in the Organization
`422`	`INTEGRATION_ACCOUNT_PREVIEW_NOT_SUPPORTED_ERROR`	The Integration isn’t `rho`. `params.integrationId` and `params.kind`
`422`	`INTEGRATION_PROVIDER_UNAUTHORIZED_ERROR`	Rho no longer accepts the token: it expired or was revoked. Replace the token
`422`	`INTEGRATION_CONNECT_REJECTED_ERROR`	The token can no longer read the business or its accounts
`503`	`INTEGRATION_PROVIDER_UNREACHABLE_ERROR`	Rho can’t be reached right now, or it limits the token’s requests. Retry later

Replace the Rho token

Before the token expires, or after you revoke it, create a new token in Rho with the same scopes. Then replace it: in the app, open the Integration’s panel and click Reemplazar clave de API. The new token must belong to the same business, or the replacement answers 409 with INTEGRATION_GRANT_MISMATCH_ERROR and the stored token stays. Then revoke the old token in Rho.

Disconnect Rho

DELETE /integrations/:integrationId, or disconnecting from the Integration’s panel, removes the token Sintropix stores. Rho keeps the token working until you revoke it there too, under Settings → API → Access Tokens.

Stripe

A stripe Integration connects one Stripe account with read-only access. Sintropix only reads: it never charges, refunds, or withdraws money. It can feed a Bank Account with each currency of the account’s Stripe payments balance, through a bank feed.

Connect Stripe

You connect Stripe from the app, because Stripe asks for consent in a browser:

Open Configuración → Integraciones, click Conectar integración, and pick Stripe, under the Pagos tag.
Continue on Stripe, pick the account to connect, and accept the read permissions of the Sintropix Stripe App. This installs the App in that account.

When you return, the Integration’s panel shows what the connection reaches: the account’s business name, País, Moneda por defecto, and Modo (En vivo or Prueba). The Integration object carries the same facts in accountName, country, defaultCurrency, and mode. If you cancel on Stripe, nothing is connected. Each Stripe account can be connected only once.

Disconnect Stripe

Disconnecting uninstalls the Sintropix Stripe App from the account, then removes the Integration. See DELETE /integrations/:integrationId.

Notion

A notion Integration connects one Notion workspace with read-only access to the pages and databases you share with Sintropix. Sintropix never writes to Notion. It stores nothing of what a database holds and feeds nothing yet: you can list the databases and preview each one.

Connect Notion

You connect Notion from the app, because Notion asks for consent in a browser:

Open Configuración → Integraciones, click Conectar integración, and pick Notion.
Continue on Notion, pick the workspace, and pick the pages or databases you share with Sintropix.

When you return, the Integration’s panel lists the databases the connection reaches under Bases en Notion. To reach another database later, open it in Notion and share it with the Sintropix connection from its ••• menu, under Conexiones. Through the API, list the Provider Accounts: each one is a database, and its id is the data source id the preview takes.

GET `/integrations/:integrationId/notion-data-sources/:dataSourceId/preview`

GET /api/organizations/:organizationId/integrations/:integrationId/notion-data-sources/:dataSourceId/preview Read one Notion database: its properties and its latest 20 pages, newest first. Sintropix reads it from Notion on every request and stores nothing. A viewer, or an API key confined to one Entity, receives 403 with PERMISSION_DENIED_ERROR. Response

Field	Type	Description
`dataSourceId`	string	The database’s data source id at Notion.
`title`	string	The database title.
`url`	string	The database in Notion.
`properties`	array	Each property of the database, as `{ propertyId, name, type }`.
`pages`	array	Up to 20 pages, newest first. Each is `{ pageId, url, createdTime, values }`, where `values` holds one value per property.

type is one of title, rich_text, number, select, multi_select, status, date, people, files, checkbox, url, email, phone_number, formula, relation, rollup, created_time, created_by, last_edited_time, last_edited_by, or unique_id. Notion adds property types over time, and a type Sintropix doesn’t read yet is null. Its values read as text with text: null. Each value carries the propertyId it belongs to and a kind:

`kind`	Fields	Properties it reads
`text`	`text` (string or null)	A title, text, select, status, multi-select, person, URL, email, phone number, or unique id. A multi-select or several people join their names with commas. A relation reads as the number of linked pages.
`number`	`number` (number or null)	A number, or a formula or rollup that gives a number.
`checkbox`	`checked` (boolean)	A checkbox, or a formula that gives true or false.
`date`	`start`, `end` (string or null)	A date, a date range, the created or last edited time, or a formula or rollup that gives a date. Each is a date or a date-time, as Notion states it.
`files`	`files` (array)	A files property. Each file is `{ name, url, expiresAt }`.

A link to a file Notion hosts expires after an hour, at expiresAt. Read the preview again instead of storing the link. A link to a file hosted elsewhere has expiresAt: null.

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/integrations/$INTEGRATION_ID/notion-data-sources/$DATA_SOURCE_ID/preview" \
  -H "x-api-key: $SINTROPIX_API_KEY"

{
  "dataSourceId": "2a1f4c3e-8b7d-4e6a-9c5b-1d0e3f2a4b6c",
  "title": "Rendiciones",
  "url": "https://www.notion.so/2a1f4c3e8b7d4e6a9c5b1d0e3f2a4b6c",
  "properties": [
    { "propertyId": "title", "name": "Gasto", "type": "title" },
    { "propertyId": "a%3Bb1", "name": "Monto", "type": "number" }
  ],
  "pages": [
    {
      "pageId": "7c3e1a2b-4d5f-4a6b-8c9d-0e1f2a3b4c5d",
      "url": "https://www.notion.so/7c3e1a2b4d5f4a6b8c9d0e1f2a3b4c5d",
      "createdTime": "2026-10-26T14:12:00.000Z",
      "values": [
        { "kind": "text", "propertyId": "title", "text": "Almuerzo con cliente" },
        { "kind": "number", "propertyId": "a%3Bb1", "number": 32500 }
      ]
    }
  ]
}

Status	`code`	When
`404`	`INTEGRATION_DATA_SOURCE_NOT_FOUND_ERROR`	The connection doesn’t reach the database: nobody shared it with Sintropix, or it no longer exists. `params` carries `integrationId` and `dataSourceId`. Share the database with the connection in Notion.
`422`	`INTEGRATION_DATA_SOURCE_PREVIEW_NOT_SUPPORTED_ERROR`	The Integration isn’t `notion`. `params` carries `integrationId` and `kind`.

Disconnect Notion

Disconnecting revokes Sintropix’s access at Notion, then removes the Integration. See DELETE /integrations/:integrationId. The connection stays in the workspace until you remove it in Notion too, under Configuración → Conexiones.

Portal Logins

A Portal Login is the login of a portal that no Provider reads. Unlike an Integration, a Portal Login belongs to one Entity, and its routes live under /api/entities/:entityId/portal-logins. Sintropix stores the login and the password encrypted and uses them only to read the portal. No read ever returns them, so not even you can see them again in Sintropix. A Portal Login has one of four kinds:

Kind	Portal	What you store
`bank_login`	A bank’s portal	The bank, picked from the Banks catalog, plus the RUT and the password you sign in with
`getnet_login`	The Getnet merchant portal	The username or email, and the password you sign in with
`sii_login`	The SII, as a company or as a person. To connect the SII, use the SII Integration instead	The taxpayer type, plus the RUT and the SII password (clave) you sign in with
`clay_login`	Clay, the Chilean ERP you migrate your books from, so the Sintropix team can migrate them	A name you choose, plus either an API key or the username and password you sign in with

Sintropix doesn’t sign in to the portal when you store a Portal Login, so a wrong login or password isn’t refused. A Portal Login has no health status: it’s stored, never “working” or “failed”. To change the password, delete the Portal Login and store it again. In the app, connect one from Configuración → Integraciones: pick your bank by its name, or pick Getnet or Clay (under the ERP tag). Pick the Entidad legal the login belongs to. It’s preset when the Organization has only one Entity. For Clay, give it a Nombre (prefilled as “Clay”) and pick how it signs in: API key or Usuario y clave. Name each Clay Login after the company it holds, so you can store one per company you migrate. A Portal Login shows in the list with the status Clave guardada.

A client or staff caller can store and delete Portal Logins. A viewer can only list them. See Access and roles.

Field	Type	Description
`id`	uuid	Portal Login id.
`entityId`	uuid	Owning Entity.
`kind`	`bank_login` \| `getnet_login` \| `sii_login` \| `clay_login`	The kind of portal.
`label`	string	The portal’s name. For a `bank_login`, the bank’s name in the Banks catalog. For a `getnet_login`, always `Getnet`. For a `sii_login`, `SII Empresa` or `SII Persona`, by its `holderType`. For a `clay_login`, the name you gave it.
`bankCode`	string \| null	For a `bank_login`, the bank’s three-digit CMF code. `null` for every other kind.
`createdAt`, `updatedAt`	ISO 8601 timestamp	When the Portal Login was stored and last changed.

POST `/portal-logins`

Store a Portal Login for the Entity. Body. The shape depends on kind. Every kind takes an id:

Field	Type	Required	Description
`id`	uuid	Yes	Client-generated id. Retrying with the same id is answered `409` (`CREDENTIAL_ALREADY_EXISTS_ERROR`).
`kind`	`bank_login` \| `getnet_login` \| `sii_login` \| `clay_login`	Yes	The kind of portal.

Each kind adds its own fields:

Kind	Field	Type	Description
`bank_login`	`bankCode`	string	The bank’s three-digit CMF code, from `GET /banks`, for example `001` for Banco de Chile. A code the catalog doesn’t hold is refused with `400` (`CREDENTIAL_BANK_UNKNOWN_ERROR`).
`bank_login`	`rut`	string	The RUT you sign in to the bank with. Dots, spaces, and the hyphen are optional, and a lowercase `k` is accepted. A RUT whose check digit doesn’t match is refused with `400` (`RUT_INVALID_ERROR`).
`bank_login`	`password`	string	The bank password. Must be non-empty.
`getnet_login`	`username`	string	The username or email you sign in to the Getnet portal with. Must be non-empty.
`getnet_login`	`password`	string	The Getnet password. Must be non-empty.
`sii_login`	`holderType`	`business` \| `individual`	Whose SII login it is: `business` for the company, `individual` for a person, such as its legal representative.
`sii_login`	`rut`	string	The RUT you sign in to the SII with. Same format and check-digit rule as the `bank_login` `rut`.
`sii_login`	`password`	string	The SII password (clave). Must be non-empty.
`clay_login`	`label`	string	The name you give this Clay Login, for example the company it holds. Whitespace is trimmed and must be non-empty.
`clay_login`	`method`	`api_key` \| `password`	How Clay is opened: with an API key, or with the username and password of the Clay web app.
`clay_login`	`apiKey`	string	The Clay API key. Required, and must be non-empty, when `method` is `api_key`.
`clay_login`	`username`	string	The username you sign in to Clay with. Required, and must be non-empty, when `method` is `password`.
`clay_login`	`password`	string	The Clay password. Required, and must be non-empty, when `method` is `password`.

Each name can be used once per Entity. Sintropix names a Bank Login after its bank, so an Entity holds at most one Bank Login per bank. A second one for the same bank is refused with 409 (CREDENTIAL_LABEL_ALREADY_USED_ERROR). A bank_login body takes no label. Sintropix names every Getnet Login Getnet, so an Entity holds at most one. A second Getnet Login is refused with the same error. To store another Getnet login, delete the first one. Sintropix names an SII Login by its holderType: SII Empresa for business and SII Persona for individual. An Entity holds at most one of each, and a second one of the same holderType is refused with the same error. A sii_login body takes no label. You name each Clay Login, so an Entity can hold as many as it needs. A Clay Login whose name the Entity already uses is refused with the same error.

Response (201): the Portal Login object.

curl -X POST "https://api.sintropix.com/api/entities/$ENTITY_ID/portal-logins" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "5c6d7e8f-9a0b-4c1d-8e2f-3a4b5c6d7e8f",
    "kind": "bank_login",
    "bankCode": "001",
    "rut": "12.345.678-5",
    "password": "my-bank-password"
  }'

{
  "id": "5c6d7e8f-9a0b-4c1d-8e2f-3a4b5c6d7e8f",
  "entityId": "8b0a7d5e-6a3c-4f2b-9e1d-2c4b6a8f0e21",
  "kind": "bank_login",
  "label": "Banco de Chile",
  "bankCode": "001",
  "createdAt": "2026-10-05T14:00:00.000Z",
  "updatedAt": "2026-10-05T14:00:00.000Z"
}

Store a Getnet Login:

curl -X POST "https://api.sintropix.com/api/entities/$ENTITY_ID/portal-logins" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "6d7e8f9a-0b1c-4d2e-9f3a-4b5c6d7e8f9a",
    "kind": "getnet_login",
    "username": "[email protected]",
    "password": "my-getnet-password"
  }'

Store the company’s SII Login:

curl -X POST "https://api.sintropix.com/api/entities/$ENTITY_ID/portal-logins" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "7e8f9a0b-1c2d-4e3f-8a4b-5c6d7e8f9a0b",
    "kind": "sii_login",
    "holderType": "business",
    "rut": "76.123.456-0",
    "password": "my-sii-password"
  }'

{
  "id": "7e8f9a0b-1c2d-4e3f-8a4b-5c6d7e8f9a0b",
  "entityId": "8b0a7d5e-6a3c-4f2b-9e1d-2c4b6a8f0e21",
  "kind": "sii_login",
  "label": "SII Empresa",
  "bankCode": null,
  "createdAt": "2026-10-16T14:00:00.000Z",
  "updatedAt": "2026-10-16T14:00:00.000Z"
}

Store a Clay Login with an API key:

curl -X POST "https://api.sintropix.com/api/entities/$ENTITY_ID/portal-logins" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "8f9a0b1c-2d3e-4f4a-9b5c-6d7e8f9a0b1c",
    "kind": "clay_login",
    "label": "Clay Acme SpA",
    "method": "api_key",
    "apiKey": "my-clay-api-key"
  }'

{
  "id": "8f9a0b1c-2d3e-4f4a-9b5c-6d7e8f9a0b1c",
  "entityId": "8b0a7d5e-6a3c-4f2b-9e1d-2c4b6a8f0e21",
  "kind": "clay_login",
  "label": "Clay Acme SpA",
  "bankCode": null,
  "createdAt": "2026-10-16T15:00:00.000Z",
  "updatedAt": "2026-10-16T15:00:00.000Z"
}

To store it with the username and password instead, send "method": "password" with username and password in place of apiKey.

GET `/portal-logins`

List the Entity’s Portal Logins of every kind.

Response: array of Portal Login objects.

GET `/organizations/:organizationId/portal-logins`

GET /api/organizations/:organizationId/portal-logins List the Portal Logins of every Entity of the Organization. An API key confined to one Entity gets only its own Entity’s. To store or delete a Portal Login, use the routes of its Entity.

Response: array of Portal Login objects, each with one more field, entityName: the name of the Entity that holds it.

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/portal-logins" \
  -H "x-api-key: $SINTROPIX_API_KEY"

DELETE `/portal-logins/:portalLoginId`

Delete a Portal Login and its stored login and password. Sintropix stops reading the portal with it. Your login at the portal is unchanged. An id that isn’t one of the Entity’s Portal Logins answers 404 (CREDENTIAL_NOT_FOUND_ERROR).

Response: the deleted Portal Login object.

curl -X DELETE "https://api.sintropix.com/api/entities/$ENTITY_ID/portal-logins/$PORTAL_LOGIN_ID" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent"

Status codes

Status	Meaning
`200`	Success on `GET`, `PUT`, `DELETE`, and a General Ledger Export, including one Google refused.
`201`	Integration, Mailbox, or Portal Login created, or an email attachment copied into an Entity.
`400`	Validation error (including a Portal Login RUT that fails its check digit, `RUT_INVALID_ERROR`, or a Bank Login `bankCode` the Banks catalog doesn’t hold, `CREDENTIAL_BANK_UNKNOWN_ERROR`), missing `x-audit-actor` on a key-authenticated mutation, or a General Ledger Export while an Entity other than the one of the picked Book keeps Books (`BOOK_REQUIRED_ERROR`).
`403`	A caller other than `staff` creates a Fintoc Link Intent or reconnects a Fintoc Integration, or an API key confined to one Entity connects, renews, or disconnects an Integration or runs a General Ledger Export, or a `viewer` or an API key confined to one Entity reads or copies email, reads a Mailbox’s Conversations, or reads the expenses of an Xpendit account or the preview of a Notion database, or an API key confined to one Entity creates a Mailbox (`PERMISSION_DENIED_ERROR`).
`404`	Organization, Entity, Integration (`INTEGRATION_NOT_FOUND_ERROR`), Portal Login (`CREDENTIAL_NOT_FOUND_ERROR`), Mailbox (`MAILBOX_NOT_FOUND_ERROR`), Conversation (`CONVERSATION_NOT_FOUND_ERROR`), email (`INTEGRATION_EMAIL_NOT_FOUND_ERROR`), email attachment (`INTEGRATION_EMAIL_ATTACHMENT_NOT_FOUND_ERROR`), or a Notion database the connection doesn’t reach (`INTEGRATION_DATA_SOURCE_NOT_FOUND_ERROR`) not found.
`409`	Integration id already exists, the Organization has no email domain for a Mailbox (`MAILBOX_EMAIL_DOMAIN_NOT_SET_ERROR`), a Mailbox address already exists (`MAILBOX_ALREADY_EXISTS_ERROR`), a disconnect names a Mailbox (`MAILBOX_NOT_REMOVABLE_ERROR`), the Organization’s email domain no longer receives email (`EMAIL_DOMAIN_NOT_OPEN_ERROR`), the external account, such as an SII RUT, is already connected (`INTEGRATION_ACCOUNT_ALREADY_CONNECTED_ERROR`), a reconnect names another grant or a non-Fintoc Integration, or a replaced Xpendit key opens another enterprise or a replaced Rho token another business (`INTEGRATION_GRANT_MISMATCH_ERROR`), a Portal Login id already exists (`CREDENTIAL_ALREADY_EXISTS_ERROR`), or a Portal Login names a portal the Entity already uses, including a second Bank Login for the same bank, a second Getnet Login, a second SII Login of the same `holderType`, or a Clay Login whose name is in use (`CREDENTIAL_LABEL_ALREADY_USED_ERROR`), or another General Ledger Export of the Integration is still running (`GENERAL_LEDGER_EXPORT_RUNNING_ERROR`).
`410`	The Provider no longer holds the grant (`INTEGRATION_GRANT_GONE_ERROR`). Disconnect the Integration and connect it again.
`422`	The Provider refused the credentials (`INTEGRATION_CONNECT_REJECTED_ERROR`), Xpendit, Buk, or Rho refused the API key (`INTEGRATION_PROVIDER_UNAUTHORIZED_ERROR`), an API key replacement names an Integration that isn’t `xpendit`, `buk`, or `rho` (`INTEGRATION_TOKEN_REPLACEMENT_NOT_SUPPORTED_ERROR`), an Xpendit expense or Provider Account read names an Integration that has none (`INTEGRATION_EXPENSES_NOT_SUPPORTED_ERROR`), a Provider account carries a currency Sintropix does not know (`INTEGRATION_CURRENCY_UNKNOWN_ERROR`), a General Ledger Export names an Integration that isn’t `google_sheets` (`GENERAL_LEDGER_EXPORT_NOT_SUPPORTED_ERROR`), the SII refused a Clave (`SII_CLAVE_REFUSED_ERROR`), a legal representative’s Clave names the company’s own RUT (`SII_REPRESENTATIVE_RUT_IS_TAXPAYER_RUT_ERROR`), the legal representative’s Clave names an Integration that isn’t `sii_mirror` (`INTEGRATION_REPRESENTATIVE_CLAVE_NOT_SUPPORTED_ERROR`), an email route names an Integration that isn’t `gmail`, `outlook`, or `mailbox` (`INTEGRATION_EMAIL_NOT_SUPPORTED_ERROR`), a database preview names an Integration that isn’t `notion` (`INTEGRATION_DATA_SOURCE_PREVIEW_NOT_SUPPORTED_ERROR`), or an account preview names an Integration that isn’t `rho` (`INTEGRATION_ACCOUNT_PREVIEW_NOT_SUPPORTED_ERROR`).
`424`	The Provider refused the request (`BANK_FEED_PROVIDER_FAILURE_ERROR`, `BANK_FEED_PROVIDER_UNAUTHORIZED_ERROR`, `BANK_FEED_PROVIDER_ROLE_REFUSED_ERROR`, or `INTEGRATION_PROVIDER_FAILURE_ERROR`), the access of an email account failed (`INTEGRATION_GRANT_FAILED_ERROR`), or the Mailbox limit of the email plan is reached (`MAILBOX_LIMIT_REACHED_ERROR`). See Provider refusals.
`503`	The Provider can’t be reached right now (`BANK_FEED_PROVIDER_UNREACHABLE_ERROR` or `INTEGRATION_PROVIDER_UNREACHABLE_ERROR`), Sintropix can’t connect that Provider right now (`INTEGRATION_NOT_CONFIGURED_ERROR`), Sintropix can’t store a Portal Login right now (`CREDENTIAL_NOT_CONFIGURED_ERROR`), the SII gave no answer in time or the SII mirror is busy with that RUT (`SII_UNAVAILABLE_ERROR`), or a Mailbox can’t be created or read right now (`MAILBOX_UNAVAILABLE_ERROR`). Retry later.

⌘I

​Integrations belong to the Organization

​The Integration object

​POST /integrations

​POST /integrations/fintoc/link-intents

​POST /integrations/plaid/link-tokens

​POST /integrations/:integrationId/reconnect

​GET /integrations

​PUT /integrations/:integrationId/purpose

​DELETE /integrations/:integrationId

​SII

​Connect the SII

​The legal representative’s Clave

​PUT /integrations/:integrationId/sii-representative-clave

​GET /integrations/:integrationId/sii-representative-clave

​Gmail and Outlook

​Connect an email account

​Mailbox

​The email domain

​Create a Mailbox

​POST /integrations/mailbox

​Read a Mailbox’s Conversations

​GET /integrations/:integrationId/conversations

​GET /integrations/:integrationId/conversations/:conversationId

​A Mailbox stays

​Mailbox errors

​Read email

​Who can read email

​The Email object

​GET /integrations/:integrationId/emails

​GET /integrations/:integrationId/emails/:emailId

​POST /api/entities/:entityId/email-attachments

​Read a Mailbox’s email

​Email errors

​Google Sheets

​Connect a Google Sheet

​What the Sheet holds

​Libro mayor

​Plan de cuentas

​Dimensiones

​When the export runs

​The General Ledger Export object

​POST /integrations/:integrationId/general-ledger-exports

​Xpendit

​Connect Xpendit

​PUT /integrations/:integrationId/access-token

​Read what Xpendit holds

​GET /integrations/:integrationId/xpendit-overview

​GET /integrations/:integrationId/provider-accounts

​Disconnect Xpendit

​Buk

​Connect Buk

​Disconnect Buk

​Rho

​Create the token in Rho

​Connect Rho

​GET /integrations/:integrationId/rho-overview

​Replace the Rho token

​Disconnect Rho

​Stripe

​Connect Stripe

​Disconnect Stripe

​Notion

​Connect Notion

​GET /integrations/:integrationId/notion-data-sources/:dataSourceId/preview

​Disconnect Notion

​Portal Logins

​The Portal Login object

​POST /portal-logins

​GET /portal-logins

​GET /organizations/:organizationId/portal-logins

​DELETE /portal-logins/:portalLoginId

​Status codes

Integrations belong to the Organization

The Integration object

POST `/integrations`

POST `/integrations/fintoc/link-intents`

POST `/integrations/plaid/link-tokens`

POST `/integrations/:integrationId/reconnect`

GET `/integrations`

PUT `/integrations/:integrationId/purpose`

DELETE `/integrations/:integrationId`

SII

Connect the SII

The legal representative’s Clave

PUT `/integrations/:integrationId/sii-representative-clave`

GET `/integrations/:integrationId/sii-representative-clave`

Gmail and Outlook

Connect an email account

Mailbox

The email domain

Create a Mailbox

POST `/integrations/mailbox`

Read a Mailbox’s Conversations

GET `/integrations/:integrationId/conversations`

GET `/integrations/:integrationId/conversations/:conversationId`

A Mailbox stays

Mailbox errors

Read email

Who can read email

The Email object

GET `/integrations/:integrationId/emails`

GET `/integrations/:integrationId/emails/:emailId`

POST `/api/entities/:entityId/email-attachments`

Read a Mailbox’s email

Email errors

Google Sheets

Connect a Google Sheet

What the Sheet holds

Libro mayor

Plan de cuentas

Dimensiones

When the export runs

The General Ledger Export object

POST `/integrations/:integrationId/general-ledger-exports`

Xpendit

Connect Xpendit

PUT `/integrations/:integrationId/access-token`

Read what Xpendit holds

GET `/integrations/:integrationId/xpendit-overview`

GET `/integrations/:integrationId/provider-accounts`

Disconnect Xpendit

Buk

Connect Buk

Disconnect Buk

Rho

Create the token in Rho

Connect Rho

GET `/integrations/:integrationId/rho-overview`

Replace the Rho token

Disconnect Rho

Stripe

Connect Stripe

Disconnect Stripe

Notion

Connect Notion

GET `/integrations/:integrationId/notion-data-sources/:dataSourceId/preview`

Disconnect Notion

Portal Logins

The Portal Login object

POST `/portal-logins`

GET `/portal-logins`

GET `/organizations/:organizationId/portal-logins`

DELETE `/portal-logins/:portalLoginId`

Status codes