> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Elorus

The Elorus connector lets your AI agent act in each user's Elorus account. Each user connects their own Elorus API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 60 tools.

**Authentication:** API Key
**Categories:** Accounting & Finance
**Tools:** 60: 30 read, 22 write, 8 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=ELORUS)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Elorus connection

   In **AgentKit > Connections**, create an Elorus connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'elorus'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Elorus:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'elorus_bills_list',
     toolInput: { organization_id: '1234567890123456' },
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "elorus"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Elorus:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={"organization_id":"1234567890123456"},
       tool_name="elorus_bills_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Elorus credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'elorus_bill_get',
  toolInput: {
    id: '<id>',
    organization_id: '<organization_id>',
  },
  connector: 'elorus',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="elorus_bill_get",
    tool_input={
        "id": "<id>",
        "organization_id": "<organization_id>",
    },
    connection_name="elorus",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `elorus_bill_get`

Get Bill · Read-only

Get one Elorus bill by ID.
Returns all of the bill's fields.
Use elorus_bills_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the bill (supplier invoice). Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_bills_list`

List Bills · Read-only

List Elorus bills with search, filters, ordering and paging.
Returns count, next, previous and results[] of bills.
Use elorus_bill_get for one bill.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `currency_code` (`string`, optional): Optionally filter by currency code. Example: EUR.
- `custom_id` (`string`, optional): Optionally filter by custom ID. Example: ABC-123-a1.
- `documenttype` (`string`, optional): Optionally filter by document type ID. Example: 4400000040000123.
- `draft` (`string`, optional): Optionally filter by draft status. The available choices are: 1, 0.
- `fpaid` (`string`, optional): Optionally filter by whether the invoice is paid or not. The available choices are: yes, no. Example: 0.
- `is_void` (`string`, optional): Optionally filter by void status. The available choices are: 1, 0.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are date, branch__branch_name, supplier__display_name, total, initial, net, draft, paid, payable, due_date, modified, created. Prepend a - to denote reverse ordering (e.g -date). Example: -created.
- `overdue` (`string`, optional): Optionally filter by whether the invoice is overdue or not. The available choices are: yes, no. Example: 1.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `pending_approval` (`string`, optional): Optionally filter by pending status. The available choices are: 1, 0.
- `period` (`string`, optional): Optionally filter results from a date period. Date period must be one of the following constants: today,current_week, current_month, current_year, last_week, last_month, last_year or in the form of this template last_ _
- `period_from` (`string`, optional): Optionally filter results from a date onwards. Must be used with the period_to parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-01.
- `period_to` (`string`, optional): Optionally filter results from a date backwards. Must be used with the period_from parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-30.
- `search` (`string`, optional): A search term. Example: Acme.
- `self_billed` (`string`, optional): Optionally filter by whether the document is self-billed or not. Can be either 1 or 0. The available choices are: 1, 0.
- `status` (`string`, optional): Optionally filter by the document's status. The available choices are: draft, pending, issued, partial, unpaid, overdue, paid, void.
- `supplier` (`string`, optional): Optionally filter by supplier ID. Example: 3300000040000100.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_cash_payment_get`

Get Cash Payment · Read-only

Get one Elorus cash payment by ID.
Returns all of the cash payment's fields.
Use elorus_cash_payments_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the cash payment (money paid out). Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_cash_payments_list`

List Cash Payments · Read-only

List Elorus cash payments with search, filters, ordering and paging.
Returns count, next, previous and results[] of cash payments.
Use elorus_cash_payment_get for one cash payment.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `contact` (`string`, optional): Optionally filter by contact ID. Example: 3300000040000100.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `creditnote` (`string`, optional): Optionally filter by credit note ID. Example: 1.
- `currency_code` (`string`, optional): Optionally filter by currency code. Example: EUR.
- `custom_id` (`string`, optional): Optionally filter by custom ID. Example: ABC-123-a1.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are date, amount, branch__branch_name, contact__display_name, modified, created. Prepend a - to denote reverse ordering (e.g -date). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `period` (`string`, optional): Optionally filter results from a date period. Date period must be one of the following constants: today,current_week, current_month, current_year, last_week, last_month, last_year or in the form of this template last_ _
- `period_from` (`string`, optional): Optionally filter results from a date onwards. Must be used with the period_to parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-01.
- `period_to` (`string`, optional): Optionally filter results from a date backwards. Must be used with the period_from parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-30.
- `purchase` (`string`, optional): Optionally filter by bill ID. Example: 1.
- `search` (`string`, optional): A search term. Example: Acme.
- `transaction_type` (`string`, optional): Optionally filter by transaction type. Either dp, ip or cnp

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_cash_receipt_get`

Get Cash Receipt · Read-only

Get one Elorus cash receipt by ID.
Returns all of the cash receipt's fields.
Use elorus_cash_receipts_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the cash receipt (money received). Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_cash_receipts_list`

List Cash Receipts · Read-only

List Elorus cash receipts with search, filters, ordering and paging.
Returns count, next, previous and results[] of cash receipts.
Use elorus_cash_receipt_get for one cash receipt.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `contact` (`string`, optional): Optionally filter by contact ID. Example: 3300000040000100.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `currency_code` (`string`, optional): Optionally filter by currency code. Example: EUR.
- `custom_id` (`string`, optional): Optionally filter by custom ID. Example: ABC-123-a1.
- `invoice` (`string`, optional): Optionally filter by invoice ID. Example: 8800000040088865.
- `is_void` (`string`, optional): Optionally filter by void status. The available choices are: 1, 0.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are date, amount, branch__branch_name, contact__display_name, modified, created. Prepend a - to denote reverse ordering (e.g -date). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `pending_approval` (`string`, optional): Optionally filter by pending status. The available choices are: 1, 0.
- `period` (`string`, optional): Optionally filter results from a date period. Date period must be one of the following constants: today,current_week, current_month, current_year, last_week, last_month, last_year or in the form of this template last_ _
- `period_from` (`string`, optional): Optionally filter results from a date onwards. Must be used with the period_to parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-01.
- `period_to` (`string`, optional): Optionally filter results from a date backwards. Must be used with the period_from parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-30.
- `purchasecreditnote` (`string`, optional): Optionally filter by supplier credit ID. Example: 1.
- `search` (`string`, optional): A search term. Example: Acme.
- `transaction_type` (`string`, optional): Optionally filter by transaction type. Either dp, ip or cnp

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_contact_get`

Get Contact · Read-only

Get one Elorus contact by ID.
Returns all of the contact's fields.
Use elorus_contacts_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the contact (client or supplier). Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_contacts_list`

List Contacts · Read-only

List Elorus contacts with search, filters, ordering and paging.
Returns count, next, previous and results[] of contacts.
Use elorus_contact_get for one contact.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `active` (`string`, optional): Whether to show only active or inactive (archived) records. The available choices are: 1, 0.
- `company` (`string`, optional): Optionally filter by company. Example: Acme Inc..
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ctype` (`string`, optional): Optionally filter by contact type. The available choices are: client, supplier.
- `custom_id` (`string`, optional): Optionally filter by custom ID. Example: ABC-123-a1.
- `letter` (`string`, optional): Optionally filter by starting letter. Refers to the contact's "display_name." Example: A.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are display_name, profession, vat_number, modified, created. Prepend a - to denote reverse ordering (e.g -display_name). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `profession` (`string`, optional): Optionally filter by profession. Example: Consultant.
- `search` (`string`, optional): A search term. Example: Acme.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_credit_note_get`

Get Credit Note · Read-only

Get one Elorus credit note by ID.
Returns all of the credit note's fields.
Use elorus_credit_notes_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the credit note. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_credit_notes_list`

List Credit Notes · Read-only

List Elorus credit notes with search, filters, ordering and paging.
Returns count, next, previous and results[] of credit notes.
Use elorus_credit_note_get for one credit note.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `client` (`string`, optional): Optionally filter by client ID. Example: 3300000040000100.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `currency_code` (`string`, optional): Optionally filter by currency code. Example: EUR.
- `custom_id` (`string`, optional): Optionally filter by custom ID. Example: ABC-123-a1.
- `documenttype` (`string`, optional): Optionally filter by document type ID. Example: 4400000040000123.
- `draft` (`string`, optional): Optionally filter by draft status. The available choices are: 1, 0.
- `fpaid` (`string`, optional): Optionally filter by whether the invoice is paid or not. The available choices are: 1, 0.
- `is_void` (`string`, optional): Optionally filter by void status. The available choices are: 1, 0.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are date, documenttype__title, client__display_name, total, initial, net, draft, paid, payable, branch__branch_name, number, sequence_flat, modified, created. Prepend a - to denote reverse ordering (e.g -date). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `pending_approval` (`string`, optional): Optionally filter by pending status. The available choices are: 1, 0.
- `period` (`string`, optional): Optionally filter results from a date period. Date period must be one of the following constants: today,current_week, current_month, current_year, last_week, last_month, last_year or in the form of this template last_ _
- `period_from` (`string`, optional): Optionally filter results from a date onwards. Must be used with the period_to parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-01.
- `period_to` (`string`, optional): Optionally filter results from a date backwards. Must be used with the period_from parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-30.
- `search` (`string`, optional): A search term. Example: Acme.
- `sequence` (`string`, optional): Optionally filter by the numbering sequence. Example: A.
- `status` (`string`, optional): Optionally filter by the document's status. The available choices are: draft, pending, issued, partial, unpaid, paid, void.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_delivery_notes_list`

List Delivery Notes · Read-only

List Elorus delivery notes with search, ordering and paging.
Returns count, next, previous and results[] of delivery notes.
Use their IDs when creating or updating other records.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `contact` (`string`, optional): Optionally filter by contact ID. Example: 3300000040000100.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `currency_code` (`string`, optional): Optionally filter by currency code. Example: EUR.
- `custom_id` (`string`, optional): Optionally filter by custom ID. Example: ABC-123-a1.
- `documenttype` (`string`, optional): Optionally filter by document type ID. Example: 4400000040000123.
- `draft` (`string`, optional): Optionally filter by draft status. The available choices are: 1, 0.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are date, documenttype__title, branch__branch_name, contact__display_name, total, initial, net, draft, number, sequence_flat, modified, created. Prepend a - to denote reverse ordering (e.g -date). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `period` (`string`, optional): Optionally filter results from a date period. Date period must be one of the following constants: today,current_week, current_month, current_year, last_week, last_month, last_year or in the form of this template last_ _
- `period_from` (`string`, optional): Optionally filter results from a date onwards. Must be used with the period_to parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-01.
- `period_to` (`string`, optional): Optionally filter results from a date backwards. Must be used with the period_from parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-30.
- `search` (`string`, optional): A search term. Example: Acme.
- `sequence` (`string`, optional): Optionally filter by the numbering sequence. Example: A.
- `status` (`string`, optional): Optionally filter by the document's status. Available choices are draft and issued The available choices are: draft, issued. Example: unpaid.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_document_types_list`

List Document Types · Read-only

List Elorus document types with search, ordering and paging.
Returns count, next, previous and results[] of document types.
Use their IDs when creating or updating other records.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `active` (`string`, optional): Whether to show only active or inactive (archived) records. The available choices are: 1, 0.
- `always_self_billed` (`string`, optional): A base custom filter for boolean fields. The available choices are: 1, 0.
- `application` (`string`, optional): Optional filter. The available choices are: 1, 2, 3, 4, 5. Example: sales.
- `is_delivery_note` (`string`, optional): A base custom filter for boolean fields. The available choices are: 1, 0.
- `is_reverse_delivery_note` (`string`, optional): A base custom filter for boolean fields. The available choices are: 1, 0.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are title, active, application, created, modified. Prepend a - to denote reverse ordering (e.g -title). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `search` (`string`, optional): A search term. Example: Acme.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_email_templates_list`

List Email Templates · Read-only

List Elorus email templates with search, ordering and paging.
Returns count, next, previous and results[] of email templates.
Use their IDs when creating or updating other records.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `email_type` (`string`, optional): Optional filter. The available choices are: invoice, estimate, purchase, cashreceipt, client_statement.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are subject, email_type, message, default_for_language, default, modified, created. Prepend a - to denote reverse ordering (e.g -subject). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `search` (`string`, optional): A search term. Example: Acme.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_estimate_get`

Get Estimate · Read-only

Get one Elorus estimate by ID.
Returns all of the estimate's fields.
Use elorus_estimates_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the estimate. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_estimates_list`

List Estimates · Read-only

List Elorus estimates with search, filters, ordering and paging.
Returns count, next, previous and results[] of estimates.
Use elorus_estimate_get for one estimate.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `accept_status` (`string`, optional): Optionally filter by accept status. The available choices are: accepted, rejected, empty.
- `active` (`string`, optional): Whether to show only active or inactive (archived) records. The available choices are: 1, 0.
- `client` (`string`, optional): Optionally filter by client ID. Example: 3300000040000100.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `currency_code` (`string`, optional): Optionally filter by currency code. Example: EUR.
- `custom_id` (`string`, optional): Optionally filter by custom ID. Example: ABC-123-a1.
- `documenttype` (`string`, optional): Optionally filter by document type ID. Example: 4400000040000123.
- `draft` (`string`, optional): Optionally filter by draft status. The available choices are: 1, 0.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are date, documenttype__title, branch__branch_name, client__display_name, total, initial, net, draft, number, sequence_flat, modified, created. Prepend a - to denote reverse ordering (e.g -date). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `period` (`string`, optional): Optionally filter results from a date period. Date period must be one of the following constants: today,current_week, current_month, current_year, last_week, last_month, last_year or in the form of this template last_ _
- `period_from` (`string`, optional): Optionally filter results from a date onwards. Must be used with the period_to parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-01.
- `period_to` (`string`, optional): Optionally filter results from a date backwards. Must be used with the period_from parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-30.
- `search` (`string`, optional): A search term. Example: Acme.
- `sequence` (`string`, optional): Optionally filter by the numbering sequence. Example: A.
- `status` (`string`, optional): Optionally filter by the document's status. The available choices are: draft, issued, accepted, rejected, invoiced. Example: unpaid.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_expense_categories_list`

List Expense Categories · Read-only

List Elorus expense categorys with search, ordering and paging.
Returns count, next, previous and results[] of expense categorys.
Use their IDs when creating or updating other records.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `active` (`string`, optional): Whether to show only active or inactive (archived) records. The available choices are: 1, 0.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are title, created, modified. Prepend a - to denote reverse ordering (e.g -title). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `search` (`string`, optional): A search term. Example: Acme.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_expense_get`

Get Expense · Read-only

Get one Elorus expense by ID.
Returns all of the expense's fields.
Use elorus_expenses_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the expense. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_expenses_list`

List Expenses · Read-only

List Elorus expenses with search, filters, ordering and paging.
Returns count, next, previous and results[] of expenses.
Use elorus_expense_get for one expense.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `branch_id` (`string`, optional): Optionally filter by branch ID. Example: 5500000050000678.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `currency_code` (`string`, optional): Optionally filter by currency code. Example: EUR.
- `custom_id` (`string`, optional): Optionally filter by custom ID. Example: ABC-123-a1.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are date, branch__branch_name, supplier__display_name, net, total, created, modified, modified, created. Prepend a - to denote reverse ordering (e.g -date). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `period` (`string`, optional): Optionally filter results from a date period. Date period must be one of the following constants: today,current_week, current_month, current_year, last_week, last_month, last_year or in the form of this template last_ _
- `period_from` (`string`, optional): Optionally filter results from a date onwards. Must be used with the period_to parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-01.
- `period_to` (`string`, optional): Optionally filter results from a date backwards. Must be used with the period_from parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-30.
- `search` (`string`, optional): A search term. Example: Acme.
- `supplier` (`string`, optional): Optionally filter by supplier ID. Example: 3300000040000100.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_invoice_get`

Get Invoice · Read-only

Get one Elorus invoice by ID.
Returns all of the invoice's fields.
Use elorus_invoices_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the invoice. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_invoices_list`

List Invoices · Read-only

List Elorus invoices with search, filters, ordering and paging.
Returns count, next, previous and results[] of invoices.
Use elorus_invoice_get for one invoice.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `client` (`string`, optional): Optionally filter by client ID. Example: 3300000040000100.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `currency_code` (`string`, optional): Optionally filter by currency code. Example: EUR.
- `custom_id` (`string`, optional): Optionally filter by custom ID. Example: ABC-123-a1.
- `documenttype` (`string`, optional): Optionally filter by document type ID. Example: 4400000040000123.
- `draft` (`string`, optional): Optionally filter by draft status. The available choices are: 1, 0.
- `fpaid` (`string`, optional): Optionally filter by whether the invoice is paid or not. The available choices are: 1, 0.
- `is_void` (`string`, optional): Optionally filter by void status. The available choices are: 1, 0.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are date, documenttype__title, client__display_name, total, initial, net, draft, paid, payable, number, sequence_flat, due_date, branch__branch_name, modified, created. Prepend a - to denote reverse ordering (e.g -date). Example: -created.
- `overdue` (`string`, optional): Optionally filter by whether the invoice is overdue or not. The available choices are: 1, 0.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `pending_approval` (`string`, optional): Optionally filter by pending status. The available choices are: 1, 0.
- `period` (`string`, optional): Optionally filter results from a date period. Date period must be one of the following constants: today,current_week, current_month, current_year, last_week, last_month, last_year or in the form of this template last_ _
- `period_from` (`string`, optional): Optionally filter results from a date onwards. Must be used with the period_to parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-01.
- `period_to` (`string`, optional): Optionally filter results from a date backwards. Must be used with the period_from parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-30.
- `search` (`string`, optional): A search term. Example: Acme.
- `sequence` (`string`, optional): Optionally filter by the numbering sequence. Example: A.
- `status` (`string`, optional): Optionally filter by the document's status. The available choices are: draft, pending, issued, partial, unpaid, overdue, paid, void.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_product_get`

Get Product Or Service · Read-only

Get one Elorus product or service by ID.
Returns all of the product or service's fields.
Use elorus_products_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the product or service. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_products_list`

List Products · Read-only

List Elorus product or services with search, filters, ordering and paging.
Returns count, next, previous and results[] of product or services.
Use elorus_product_get for one product or service.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `active` (`string`, optional): Whether to show only active or inactive (archived) records. The available choices are: 1, 0.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `custom_id` (`string`, optional): Optionally filter by custom ID. Example: ABC-123-a1.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are title, sales, sale_value, purchases, purchase_value, manage, code, modified, created. Prepend a - to denote reverse ordering (e.g -title). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `purchases` (`string`, optional): Optionally filter by purchase status. The available choices are: 1, 0.
- `sales` (`string`, optional): Optionally filter by sales status. The available choices are: 1, 0.
- `search` (`string`, optional): A search term. Example: Acme.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_project_get`

Get Project · Read-only

Get one Elorus project by ID.
Returns all of the project's fields.
Use elorus_projects_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the project. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_projects_list`

List Projects · Read-only

List Elorus projects with search, filters, ordering and paging.
Returns count, next, previous and results[] of projects.
Use elorus_project_get for one project.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `active` (`string`, optional): Whether to show only active or inactive (archived) records. The available choices are: 1, 0.
- `billing_method` (`string`, optional): Optional filter. The available choices are: fixed_cost, project_rate, task_rate, assignee_rate, non_billable. Example: hourly.
- `client` (`string`, optional): Optionally filter by client ID. Example: 3300000040000100.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are name, client__display_name, created, modified. Prepend a - to denote reverse ordering (e.g -name). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `search` (`string`, optional): A search term. Example: Acme.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_recurring_invoice_get`

Get Recurring Invoice · Read-only

Get one Elorus recurring invoice by ID.
Returns all of the recurring invoice's fields.
Use elorus_recurring_invoices_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the recurring invoice. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_recurring_invoices_list`

List Recurring Invoices · Read-only

List Elorus recurring invoices with search, filters, ordering and paging.
Returns count, next, previous and results[] of recurring invoices.
Use elorus_recurring_invoice_get for one recurring invoice.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `client` (`string`, optional): Optionally filter by client ID. Example: 3300000040000100.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `currency_code` (`string`, optional): Optionally filter by currency code. Example: EUR.
- `custom_id` (`string`, optional): Optionally filter by custom ID. Example: ABC-123-a1.
- `documenttype` (`string`, optional): Optionally filter by document type ID. Example: 4400000040000123.
- `draft` (`string`, optional): Optionally filter by draft status. The available choices are: 1, 0.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are start_datetime, end_datetime, sequence_flat, documenttype__title, branch__branch_name, client__display_name, total, payable, initial, net, draft, modified, created. Prepend a - to denote reverse ordering (e.g -start_datetime). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `recurring_status` (`string`, optional): Optionally filter by recurring status. The available choices are: active, paused, expired.
- `search` (`string`, optional): A search term. Example: Acme.
- `sequence` (`string`, optional): Optionally filter by the numbering sequence. Example: A.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_tasks_list`

List Tasks · Read-only

List Elorus tasks with search, ordering and paging.
Returns count, next, previous and results[] of tasks.
Use their IDs when creating or updating other records.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `active` (`string`, optional): Whether to show only active or inactive (archived) records. The available choices are: 1, 0.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are name, hourly_rate, active, created, modified. Prepend a - to denote reverse ordering (e.g -name). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `project` (`string`, optional): Optional filter. Example: 7700000040000100.
- `search` (`string`, optional): A search term. Example: Acme.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_taxes_list`

List Taxes · Read-only

List Elorus taxs with search, ordering and paging.
Returns count, next, previous and results[] of taxs.
Use their IDs when creating or updating other records.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `active` (`string`, optional): Whether to show only active or inactive (archived) records. The available choices are: 1, 0.
- `created_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `created_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `modified_after` (`string`, optional): Optionally filter results from a date onwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-01.
- `modified_before` (`string`, optional): Optionally filter results from a date backwards. Date must be in the form of YYYY-mm-dd or ISO-formatted. Example: 2026-11-30.
- `operand` (`string`, optional): Optionally filter by operand. The available choices are: plus, minus. Example: add.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are title, operand, percentage, active, tax_type, modified, created. Prepend a - to denote reverse ordering (e.g -title). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `search` (`string`, optional): A search term. Example: Acme.
- `tax_type` (`string`, optional): Optionally filter by tax type. The available choices are: simple, vat, withholding.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_time_entries_list`

List Time Entries · Read-only

List Elorus time entrys with search, ordering and paging.
Returns count, next, previous and results[] of time entrys.
Use their IDs when creating or updating other records.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `assignee` (`string`, optional): Optional filter. Example: 1100000040000100.
- `billing_status` (`string`, optional): Optional filter. The available choices are: non-billable, billed, unbilled.
- `client` (`string`, optional): Optionally filter by client ID. Example: 3300000040000100.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are start_datetime, project__name, task__name. Prepend a - to denote reverse ordering (e.g -start_datetime). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `period` (`string`, optional): Optionally filter results from a date period. Date period must be one of the following constants: today,current_week, current_month, current_year, last_week, last_month, last_year or in the form of this template last_ _
- `period_from` (`string`, optional): Optionally filter results from a date onwards. Must be used with the period_to parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-01.
- `period_to` (`string`, optional): Optionally filter results from a date backwards. Must be used with the period_from parameter, otherwise it won't have any effect. Date must be in the form of YYYY-mm-dd. Example: 2026-11-30.
- `project` (`string`, optional): Optional filter. Example: 7700000040000100.
- `search` (`string`, optional): A search term. Example: Acme.
- `task` (`string`, optional): Optional filter. Example: 7800000040000100.
- `user_team` (`string`, optional): Filter time entries by team ID. Example: 1200000040000100.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_users_list`

List Users · Read-only

List Elorus users with search, ordering and paging.
Returns count, next, previous and results[] of users.
Use their IDs when creating or updating other records.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `active` (`string`, optional): Whether to show only active or inactive (archived) records. The available choices are: 1, 0.
- `ordering` (`string`, optional): Which field to use when ordering the results. A comma-separated list, if more than one is provided. The available fields are pk. Prepend a - to denote reverse ordering (e.g -pk). Example: -created.
- `page` (`integer`, optional): A page number within the paginated result set. Example: 1.
- `page_size` (`integer`, optional): Number of results to return per page. Default is 100. The maximum allowed value is 250.
- `search` (`string`, optional): A search term. Example: Acme.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_bill_create`

Create Bill · Write

Create an Elorus bill (supplier invoice).
Returns the new bill with its id.
Use elorus_bills_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `items` (`array`, required): Line items of a bill. Example: [{"product": "9900000040000600", "description": "Super-cool expensive socks!"}].
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `supplier` (`string`, required): ID of the associated supplier. Example: 3300000040000100.
- `billing_address` (`object`, optional): The client billing address. Example: {"address_line": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}.
- `branch` (`string`, optional): ID of the associated branch. Example: 5500000050000678.
- `calculator_mode` (`string`, optional): Automatically calculate / correct document values based on the specified calculation mode. Values: initial (Tax-exclusive), total (Tax-inclusive, after discounts), total_pre_discount (Tax-inclusive, before discounts). One of: `initial`, `total`, `total_pre_discount`.
- `currency_code` (`string`, optional): If not specified, this is set to the contact's default currency code if it exists. In other case the organization's base currency code is used. Example: EUR.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `date` (`string`, optional): The issue date. Date is in the form of YYYY-mm-dd. Example: 2018-10-25.
- `delivery_notes` (`array`, optional): A list of deliverynote IDs linked to this document. Example: ["text"].
- `dispatch_date` (`string`, optional): Date is in the form of YYYY-mm-dd. Example: 2026-11-16.
- `dispatch_time` (`string`, optional): Dispatch time Example: 09:30.
- `documenttype` (`string`, optional): Optionally, associate the record with a document type to denote the type of the received document. This field is required in case of a self-billed document. Example: 4400000040000123.
- `draft` (`boolean`, optional): If true the document is considered to be a work in progress. Example: 0.
- `due_days` (`integer`, optional): Days after the issue date, that the invoice will be considered overdue. This affects the document's due date . Use null to not set a due date. Example: 10.
- `exchange_rate` (`string`, optional): Comes into effect when the currency of the transaction is different than the base currency. Will always equal 1.00 for the base currency. Decimal rendered as string, with the . character used as a floating point. Up to 6 decimal places. Example: 1.000000.
- `loading_address` (`object`, optional): The document loading address. Example: {"address_line": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}.
- `move_purpose` (`integer`, optional): Values: 9 (Purchase). One of: `9`.
- `packages` (`array`, optional): Packages included in the transport. Example: [{"packaging_type": 1, "quantity": 2}].
- `public_notes` (`string`, optional): Applies only to self-billed invoices. These notes will appear on the PDF. Example: Notes visible on the bill..
- `reference` (`string`, optional): A reference code. Usually, the document number as specified by the supplier. Example: ABC111.
- `related_documents` (`array`, optional): A list of purchase IDs linked to this document. Example: ["text"].
- `related_entities` (`array`, optional): related_entities Example: [{"contact": "3300000040000100", "contact_display_name": "Acme Inc.", "type": 1}].
- `self_billed` (`boolean`, optional): Denotes whether this is a self-billed invoice. This value is auto-generated and depends on the bill's document type. Example: 0.
- `sequence_flat` (`string`, optional): Sequence Example: A.
- `shipping_address` (`object`, optional): The client shipping address. Example: {"address_line": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}.
- `supplier_contact_person` (`string`, optional): Applies only to self-billed invoices. The supplier's contact person, as it will appear on the PDF. Example: Jane Roe.
- `supplier_display_name` (`string`, optional): Applies only to self-billed invoices. The supplier name as it will appear on the PDF. Example: Supplies Ltd.
- `supplier_email` (`string`, optional): Applies only to self-billed invoices. The supplier email address, as it will appear on the PDF. Example: billing@supplies.example.
- `supplier_phone_number` (`string`, optional): Applies only to self-billed invoices. The supplier phone number, as it will appear on the PDF. Example: 662-222-3333.
- `supplier_profession` (`string`, optional): Applies only to self-billed invoices. The supplier profession, as it will appear on the PDF. Example: Wholesale.
- `supplier_vat_number` (`string`, optional): Supplier tax ID Example: 987654321.
- `taxes` (`array`, optional): A list of taxes to be applied (optional). If the document contains taxes that have already been applied at the line level, you may optionally resend them here. This will help specify the order that these taxes will have among the other taxes. You may also include additional taxes, which will be calculated based on the total net amount of the document. Example: [{"tax": "6600230050000705"}].
- `template` (`string`, optional): Applies only to self-billed invoices. The template to use when rendering to PDF. Example: 5500000050000999.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].
- `vehicle_number` (`string`, optional): Vehicle number Example: ABC-1234.
- `withholding_taxes` (`array`, optional): A list of withholding taxes to be applied. If the document contains withholding taxes that have already been applied at the line level, you may optionally resend them here. This will help specify the order that these taxes will have among the other withholding taxes. Example: [{"tax": "1400230050000705"}].

Example input: `{"items":[{"product":"9900000040000600","description":"Super-cool expensive socks!"}],"organization_id":"<organization_id>","supplier":"<supplier>"}`

### `elorus_bill_update`

Update Bill · Write

Update fields of an Elorus bill (PATCH). Only the fields you send change.
Returns the updated bill.
Use elorus_bill_get to read current values; use elorus_bill_void to void it.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the bill (supplier invoice). Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `draft` (`boolean`, optional): If true the document is considered to be a work in progress. Example: 0.
- `exchange_rate` (`string`, optional): Comes into effect when the currency of the transaction is different than the base currency. Will always equal 1.00 for the base currency. This field is read-only while the record is in pending approval status. Decimal rendered as string, with the . character used as a floating point. Up to 6 decimal places. Example: 1.000000.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_cash_payment_create`

Create Cash Payment · Write

Create an Elorus cash payment (money paid out).
Returns the new cash payment with its id.
Use elorus_cash_payments_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `amount` (`string`, required): Decimal rendered as string, with the . character used as a floating point. Up to 2 decimal places. Example: 100.00.
- `contact` (`string`, required): ID of the associated contact. Example: 3300000040000100.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `transaction_type` (`string`, required): Values: dp (Other payments), ip (Supplier payment), cnp (Client refund). One of: `dp`, `ip`, `cnp`.
- `branch` (`string`, optional): ID of the associated branch. Example: 5500000050000678.
- `creditnote_payments` (`array`, optional): A list of the credit notes paid via this transaction. Applies to "Client refund" transactions. Example: [{"creditnote": "1050000300010040", "amount": "20"}].
- `currency_code` (`string`, optional): If not specified, this is set to the contact's default currency code if it exists. In other case the organization's base currency code is used. Example: EUR.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `date` (`string`, optional): Date is in the form of YYYY-mm-dd. Example: 2018-10-25.
- `exchange_rate` (`string`, optional): Comes into effect when the currency of the transaction is different than the base currency. Will always equal 1.00 for the base currency. Decimal rendered as string, with the . character used as a floating point. Up to 6 decimal places. Example: 1.000000.
- `purchase_payments` (`array`, optional): A list of the bills paid via this transaction. Applies to "Supplier payment" transactions. Example: [{"purchase": "8800000040088865", "amount": "80"}].
- `title` (`string`, optional): Short description / reason. Example: A supplier invoice payment.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].

Example input: `{"amount":"<amount>","contact":"<contact>","organization_id":"<organization_id>","transaction_type":"dp"}`

### `elorus_cash_receipt_create`

Create Cash Receipt · Write

Create an Elorus cash receipt (money received).
Returns the new cash receipt with its id.
Use elorus_cash_receipts_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `amount` (`string`, required): Decimal rendered as string, with the . character used as a floating point. Up to 2 decimal places. Example: 100.00.
- `contact` (`string`, required): ID of the associated contact. Example: 3300000040000100.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `transaction_type` (`string`, required): Values: dp (Other payments), ip (Client payment), cnp (Supplier refund), icm (Income). One of: `dp`, `ip`, `cnp`, `icm`.
- `branch` (`string`, optional): ID of the associated branch. Example: 5500000050000678.
- `calculator_mode` (`string`, optional): Applies only to "Income" transactions and dictates how amounts will be calculated if there exist associated taxes. One of the following, or empty Values: initial (Tax-exclusive), total (Tax-inclusive). One of: `initial`, `total`.
- `currency_code` (`string`, optional): If not specified, this is set to the contact's default currency code if it exists. In other case the organization's base currency code is used. Example: EUR.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `date` (`string`, optional): Date is in the form of YYYY-mm-dd. Example: 2018-10-25.
- `exchange_rate` (`string`, optional): Comes into effect when the currency of the transaction is different than the base currency. Will always equal 1.00 for the base currency. Decimal rendered as string, with the . character used as a floating point. Up to 6 decimal places. Example: 1.000000.
- `income_type` (`string`, optional): Applies only to "Income" transactions. One of the following, or empty Values: contract (Contract income), rental (Rental income), other_income (Other income). One of: `contract`, `rental`, `other_income`.
- `invoice_payments` (`array`, optional): A list of the invoices paid via this transaction. Applies to "Client payment" transactions. Example: [{"invoice": "8800000040088865", "amount": "100.00"}].
- `purchasecreditnote_payments` (`array`, optional): A list of the purchase credit notes paid via this transaction. Applies to "Supplier refund" transactions. Example: [{"purchasecreditnote": "4400000040000555", "amount": "50.00"}].
- `taxes` (`array`, optional): A list of the applied tax IDs. Applies only to "Income" transactions. Example: ["6600230050000705"].
- `title` (`string`, optional): Short description / reason. Example: An invoice payment.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].

Example input: `{"amount":"<amount>","contact":"<contact>","organization_id":"<organization_id>","transaction_type":"dp"}`

### `elorus_contact_create`

Create Contact · Write

Create an Elorus contact (client or supplier).
Returns the new contact with its id.
Use elorus_contacts_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `active` (`boolean`, optional): You can archive contacts to shorten your lists without losing any data. Archived contacts cannot be invoiced, cannot login to the client portal and cannot be assigned to new projects. Example: 1.
- `addresses` (`array`, optional): A list of postal addresses. Example: [{"address": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}].
- `company` (`string`, optional): The company that the contact represents. Example: Acme Inc..
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `default_currency_code` (`string`, optional): The currency used by default when invoicing this contact. One of the following, or empty Values: AED (AED - UAE Dirham), AFN (AFN - Afghani), ALL (ALL - Lek), AMD (AMD - Armenian Dram), ANG (ANG - Netherlands Antillian Guilder), AOA (AOA - Kwanza), ARS (ARS - Argentine Peso), AUD (AUD - Australian Dollar), AWG (AWG - Aruban Florin), AZN (AZN - Azerbaijanian Manat), BAM (BAM - C... Example: USD.
- `default_language` (`string`, optional): Values: en (English), en-gb (English (United Kingdom)), el (Greek), fr (French), de (German), it (Italian), es (Spanish), bg (Bulgarian). One of: `en`, `en-gb`, `el`, `fr`, `de`, `it`, `es`, `bg`.
- `default_taxes` (`array`, optional): A list of tax IDs that should apply by default when invoicing the contact Example: ["0116700303010117"].
- `default_template` (`string`, optional): ID of the template that will be used by default when invoicing this contact. Example: 5500000050000999.
- `email` (`array`, optional): A list of email addresses. Example: [{"email": "john@doe.com", "primary": true}].
- `first_name` (`string`, optional): First name of the contact. Example: John.
- `is_client` (`boolean`, optional): Whether the contact is a client or not. Example: true.
- `is_supplier` (`boolean`, optional): Whether the contact is a supplier or not. Example: true.
- `last_name` (`string`, optional): Last name of the contact. Example: Doe.
- `phones` (`array`, optional): A list of phone numbers. Example: [{"number": "662-222-2222", "primary": true}].
- `profession` (`string`, optional): Industry / profession. Example: Consultant.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].
- `vat_number` (`string`, optional): The tax ID of the contact. Example: 123456789.

Example input: `{"organization_id":"<organization_id>"}`

### `elorus_contact_update`

Update Contact · Write

Replace an Elorus contact's data (PUT): send every field you want to keep, including required ones.
Returns the updated contact.
Use elorus_contact_get to read the current values first.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the contact (client or supplier). Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `active` (`boolean`, optional): You can archive contacts to shorten your lists without losing any data. Archived contacts cannot be invoiced, cannot login to the client portal and cannot be assigned to new projects. Example: 1.
- `addresses` (`array`, optional): A list of postal addresses. Example: [{"address": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}].
- `company` (`string`, optional): The company that the contact represents. Example: Acme Inc..
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `default_currency_code` (`string`, optional): The currency used by default when invoicing this contact. One of the following, or empty Values: AED (AED - UAE Dirham), AFN (AFN - Afghani), ALL (ALL - Lek), AMD (AMD - Armenian Dram), ANG (ANG - Netherlands Antillian Guilder), AOA (AOA - Kwanza), ARS (ARS - Argentine Peso), AUD (AUD - Australian Dollar), AWG (AWG - Aruban Florin), AZN (AZN - Azerbaijanian Manat), BAM (BAM - C... Example: USD.
- `default_language` (`string`, optional): Values: en (English), en-gb (English (United Kingdom)), el (Greek), fr (French), de (German), it (Italian), es (Spanish), bg (Bulgarian). One of: `en`, `en-gb`, `el`, `fr`, `de`, `it`, `es`, `bg`.
- `default_taxes` (`array`, optional): A list of tax IDs that should apply by default when invoicing the contact Example: ["0116700303010117"].
- `default_template` (`string`, optional): ID of the template that will be used by default when invoicing this contact. Example: 5500000050000999.
- `email` (`array`, optional): A list of email addresses. Example: [{"email": "john@doe.com", "primary": true}].
- `first_name` (`string`, optional): First name of the contact. Example: John.
- `is_client` (`boolean`, optional): Whether the contact is a client or not. Example: true.
- `is_supplier` (`boolean`, optional): Whether the contact is a supplier or not. Example: true.
- `last_name` (`string`, optional): Last name of the contact. Example: Doe.
- `phones` (`array`, optional): A list of phone numbers. Example: [{"number": "662-222-2222", "primary": true}].
- `profession` (`string`, optional): Industry / profession. Example: Consultant.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].
- `vat_number` (`string`, optional): The tax ID of the contact. Example: 123456789.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_credit_note_create`

Create Credit Note · Write

Create an Elorus credit note.
Returns the new credit note with its id.
Use elorus_credit_notes_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `client` (`string`, required): ID of the associated client. Example: 3300000040000100.
- `date` (`string`, required): The issue date. Date is in the form of YYYY-mm-dd. Example: 2018-10-25.
- `items` (`array`, required): items Example: [{"product": "9900000040000600", "title": "Pair of socks"}].
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `billing_address` (`object`, optional): The client billing address. Example: {"address_line": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}.
- `branch` (`string`, optional): ID of the associated branch. Example: 5500000050000678.
- `calculator_mode` (`string`, optional): Automatically calculate / correct document values based on the specified calculation mode. Values: initial (Tax-exclusive), total (Tax-inclusive, after discounts), total_pre_discount (Tax-inclusive, before discounts). One of: `initial`, `total`, `total_pre_discount`.
- `client_contact_person` (`string`, optional): The client's contact person, as it will appear on the PDF. Example: John Doe.
- `client_display_name` (`string`, optional): If not provided, the client name will be retrieved from the specified client contact Example: Acme Inc..
- `client_email` (`string`, optional): The client email address, as it will appear on the PDF. Example: john@doe.com.
- `client_phone_number` (`string`, optional): The client phone number, as it will appear on the PDF. Example: 662-222-2222.
- `client_profession` (`string`, optional): The client profession, as it will appear on the PDF. Example: Digital marketing.
- `client_vat_number` (`string`, optional): The client tax ID, as it will appear on the PDF. Example: 123451234.
- `currency_code` (`string`, optional): If not specified, this is set to the contact's default currency code if it exists. In other case the organization's base currency code is used. Example: EUR.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `dispatch_date` (`string`, optional): Date is in the form of YYYY-mm-dd. Example: 2026-11-16.
- `dispatch_time` (`string`, optional): Dispatch time Example: 09:30.
- `documenttype` (`string`, optional): ID of the associated document type. Example: 4400000040000123.
- `draft` (`boolean`, optional): If true the document is considered to be a work in progress. Example: 0.
- `exchange_rate` (`string`, optional): Comes into effect when the currency of the transaction is different than the base currency. Will always equal 1.00 for the base currency. Decimal rendered as string, with the . character used as a floating point. Up to 6 decimal places. Example: 1.000000.
- `loading_address` (`object`, optional): The document loading address. Example: {"address_line": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}.
- `move_purpose` (`integer`, optional): Values: 1 (Sale), 2 (Sales on Behalf of Third Parties), 5 (Return), 10 (Provision of Ships and Aircraft). One of: `1`, `2`, `5`, `10`.
- `number` (`string`, optional): Use empty string or do not send it at all, for automatic numbering. Example: 1001.
- `packages` (`array`, optional): Packages included in the transport. Example: [{"packaging_type": 1, "quantity": 2}].
- `public_notes` (`string`, optional): These notes are displayed on the document's printable form. Example: Notes visible on the credit note.
- `related_documents` (`array`, optional): A list of invoice IDs linked to this document. Example: ["4400230020000542"].
- `related_entities` (`array`, optional): Additional parties involved in the transport. This field applies only to documents that include transport information (i.e., when the is_delivery_note property of the corresponding document type is set to true) Example: [{"contact": "3300000040000100", "contact_display_name": "Acme Inc.", "type": 3}].
- `sequence_flat` (`string`, optional): Sequence Example: A.
- `shipping_address` (`object`, optional): The client shipping address. Example: {"address_line": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}.
- `taxes` (`array`, optional): A list of taxes to be applied (optional). If the document contains taxes that have already been applied at the line level, you may optionally resend them here. This will help specify the order that these taxes will have among the other taxes. You may also include additional taxes, which will be calculated based on the total net amount of the document. Example: [{"tax": "6600230050000705"}].
- `template` (`string`, optional): ID of the associated template. Example: 5500000050000999.
- `terms` (`string`, optional): These terms are displayed on the document's printable form. Example: Terms and conditions here.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].
- `vehicle_number` (`string`, optional): Vehicle number Example: ABC-1234.
- `withholding_taxes` (`array`, optional): A list of withholding taxes to be applied. If the document contains withholding taxes that have already been applied at the line level, you may optionally resend them here. This will help specify the order that these taxes will have among the other withholding taxes. Example: [{"tax": "1400230050000705"}].

Example input: `{"client":"<client>","date":"<date>","items":[{"product":"9900000040000600","title":"Pair of socks"}],"organization_id":"<organization_id>"}`

### `elorus_estimate_create`

Create Estimate · Write

Create an Elorus estimate.
Returns the new estimate with its id.
Use elorus_estimates_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `client` (`string`, required): ID of the associated client. Example: 3300000040000100.
- `items` (`array`, required): Line items of an estimate. Example: [{"product": "9900000040000600", "title": "Pair of socks"}].
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `accept_status` (`string`, optional): Whether the client has accepted / rejected the estimate. One of the following, or empty Values: accepted (Accepted), rejected (Rejected). One of: `accepted`, `rejected`.
- `billing_address` (`object`, optional): The client billing address. Example: {"address_line": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}.
- `branch` (`string`, optional): ID of the associated branch. Example: 5500000050000678.
- `calculator_mode` (`string`, optional): Automatically calculate / correct document values based on the specified calculation mode. Values: initial (Tax-exclusive), total (Tax-inclusive, after discounts), total_pre_discount (Tax-inclusive, before discounts). One of: `initial`, `total`, `total_pre_discount`.
- `client_contact_person` (`string`, optional): The client's contact person, as it will appear on the PDF. Example: John Doe.
- `client_display_name` (`string`, optional): If not provided, the client name will be retrieved from the specified client contact Example: Acme Inc..
- `client_email` (`string`, optional): The client email address, as it will appear on the PDF. Example: john@doe.com.
- `client_phone_number` (`string`, optional): The client phone number, as it will appear on the PDF. Example: 662-222-2222.
- `client_profession` (`string`, optional): The client profession, as it will appear on the PDF. Example: Digital marketing.
- `client_vat_number` (`string`, optional): The client tax ID, as it will appear on the PDF. Example: 123451234.
- `currency_code` (`string`, optional): If not specified, this is set to the contact's default currency code if it exists. In other case the organization's base currency code is used. Example: EUR.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `date` (`string`, optional): The issue date. Date is in the form of YYYY-mm-dd. Example: 2018-10-25.
- `documenttype` (`string`, optional): ID of the associated document type. Example: 4400000040000123.
- `draft` (`boolean`, optional): If true the document is considered to be a work in progress. Example: 0.
- `exchange_rate` (`string`, optional): Comes into effect when the currency of the transaction is different than the base currency. Will always equal 1.00 for the base currency. Decimal rendered as string, with the . character used as a floating point. Up to 6 decimal places. Example: 1.000000.
- `number` (`string`, optional): Use empty string or do not send it at all, for automatic numbering. Example: 1001.
- `public_notes` (`string`, optional): These notes are displayed on the document's printable form. Example: Notes visible on the estimate.
- `sequence_flat` (`string`, optional): Sequence Example: A.
- `shipping_address` (`object`, optional): The client shipping address. Example: {"address_line": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}.
- `taxes` (`array`, optional): A list of taxes to be applied (optional). If the document contains taxes that have already been applied at the line level, you may optionally resend them here. This will help specify the order that these taxes will have among the other taxes. You may also include additional taxes, which will be calculated based on the total net amount of the document. Example: [{"tax": "6600230050000705"}].
- `template` (`string`, optional): ID of the associated template. Example: 5500000050000999.
- `terms` (`string`, optional): These terms are displayed on the document's printable form. Example: Terms and conditions here.

Example input: `{"client":"<client>","items":[{"product":"9900000040000600","title":"Pair of socks"}],"organization_id":"<organization_id>"}`

### `elorus_estimate_email`

Email Estimate · Write

Email an Elorus estimate to a recipient, optionally with its PDF attached.
Returns the sent email details.
Use elorus_estimate_get to check the estimate first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `attach_pdf` (`boolean`, required): Whether to include the PDF version of the document as attachment or not. Example: true.
- `bcc` (`array`, required): A list of email addresses to blind carbon-copy the email to. Example: ["accounting@example.com"].
- `cc` (`array`, required): A list of email addresses to carbon-copy the email to. Example: ["accounting@doe.com"].
- `id` (`string`, required): ID of the estimate. Example: 4400000040000123.
- `message` (`string`, required): The email message. May contain html. Example: Hello,<br/>please find the PDF attached..
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `subject` (`string`, required): The email subject.
- `to` (`string`, required): The recipient email address. Example: someone@example.com.
- `attachments` (`array`, optional): A list of estimate attachment IDs to attach in the email Example: ["1050000300010040"].
- `sender_name` (`string`, optional): Sender display name Example: Acme Billing.
- `store_to` (`boolean`, optional): Store the recipient address on the client contact for future use. Example: true.

Example input: `{"attach_pdf":true,"bcc":["accounting@example.com"],"cc":["accounting@doe.com"],"id":"<id>","message":"<message>","organization_id":"<organization_id>","subject":"<subject>","to":"<to>"}`

### `elorus_estimate_update`

Update Estimate · Write

Update fields of an Elorus estimate (PATCH). Only the fields you send change.
Returns the updated estimate.
Use elorus_estimate_get to read current values.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the estimate. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `accept_status` (`string`, optional): Whether the client has accepted / rejected the estimate. One of the following, or empty Values: accepted (Accepted), rejected (Rejected). One of: `accepted`, `rejected`.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `draft` (`boolean`, optional): If true the document is considered to be a work in progress. Example: 0.
- `template` (`string`, optional): ID of the associated template. Example: 5500000050000999.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_expense_create`

Create Expense · Write

Create an Elorus expense.
Returns the new expense with its id.
Use elorus_expenses_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `items` (`array`, required): Line items of an expense. Example: [{"expense_category": "4416700785030129", "description": "Some text here"}].
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `branch` (`string`, optional): ID of the associated branch. Example: 5500000050000678.
- `calculator_mode` (`string`, optional): Automatically calculate / correct document values based on the specified calculation mode. Values: initial (Tax-exclusive), total (Tax-inclusive). One of: `initial`, `total`.
- `currency_code` (`string`, optional): If not specified, this is set to the contact's default currency code if it exists. In other case the organization's base currency code is used. Example: EUR.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `date` (`string`, optional): The issue date. Date is in the form of YYYY-mm-dd. Example: 2019-01-28.
- `exchange_rate` (`string`, optional): Comes into effect when the currency of the transaction is different than the base currency. Will always equal 1.00 for the base currency. Decimal rendered as string, with the . character used as a floating point. Up to 6 decimal places. Example: 1.000000.
- `net` (`string`, optional): Total net value, before any taxes are applied. Automatically calculated amount. Decimal rendered as string, with the . character used as a floating point. Up to 2 decimal places. Example: 80.00.
- `reference` (`string`, optional): A reference code. Usually, the document number as specified by the supplier. Example: ABC111.
- `supplier` (`string`, optional): ID of the associated supplier. Example: 3300000040000100.
- `taxes` (`array`, optional): A list of taxes to be applied (optional). If the document contains taxes that have already been applied at the line level, you may optionally resend them here. This will help specify the order that these taxes will have among the other taxes. You may also include additional taxes, which will be calculated based on the total net amount of the document. Example: [{"tax": "6600230050000705"}].
- `total` (`string`, optional): Automatically calculated amount. Decimal rendered as string, with the . character used as a floating point. Up to 2 decimal places. Example: 100.00.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].

Example input: `{"items":[{"expense_category":"4416700785030129","description":"Some text here"}],"organization_id":"<organization_id>"}`

### `elorus_expense_update`

Update Expense · Write

Replace an Elorus expense's data (PUT): send every field you want to keep, including required ones.
Returns the updated expense.
Use elorus_expense_get to read the current values first.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the expense. Example: 4400000040000123.
- `items` (`array`, required): Line items of an expense. Example: [{"id": "1050000300010040", "expense_category": "4416700785030129", "description": "Some text here"}].
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `branch` (`string`, optional): ID of the associated branch. Example: 5500000050000678.
- `calculator_mode` (`string`, optional): Automatically calculate / correct document values based on the specified calculation mode. Values: initial (Tax-exclusive), total (Tax-inclusive). One of: `initial`, `total`.
- `currency_code` (`string`, optional): If not specified, this is set to the contact's default currency code if it exists. In other case the organization's base currency code is used. Example: EUR.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `date` (`string`, optional): The issue date. Date is in the form of YYYY-mm-dd. Example: 2019-01-28.
- `exchange_rate` (`string`, optional): Comes into effect when the currency of the transaction is different than the base currency. Will always equal 1.00 for the base currency. Decimal rendered as string, with the . character used as a floating point. Up to 6 decimal places. Example: 1.000000.
- `net` (`string`, optional): Total net value, before any taxes are applied. Automatically calculated amount. Decimal rendered as string, with the . character used as a floating point. Up to 2 decimal places. Example: 80.00.
- `reference` (`string`, optional): A reference code. Usually, the document number as specified by the supplier. Example: ABC111.
- `supplier` (`string`, optional): ID of the associated supplier. Example: 3300000040000100.
- `taxes` (`array`, optional): A list of taxes to be applied (optional). If the document contains taxes that have already been applied at the line level, you may optionally resend them here. This will help specify the order that these taxes will have among the other taxes. You may also include additional taxes, which will be calculated based on the total net amount of the document. Example: [{"tax": "6600230050000705"}].
- `total` (`string`, optional): Automatically calculated amount. Decimal rendered as string, with the . character used as a floating point. Up to 2 decimal places. Example: 100.00.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].

Example input: `{"id":"<id>","items":[{"id":"1050000300010040","expense_category":"4416700785030129","description":"Some text here"}],"organization_id":"<organization_id>"}`

### `elorus_invoice_create`

Create Invoice · Write

Create an Elorus invoice.
Returns the new invoice with its id.
Use elorus_invoices_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `client` (`string`, required): ID of the associated client. Example: 3300000040000100.
- `date` (`string`, required): The issue date. Date is in the form of YYYY-mm-dd. Example: 2018-10-25.
- `items` (`array`, required): items Example: [{"product": "9900000040000600", "title": "Pair of socks"}].
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `billing_address` (`object`, optional): The client billing address. Example: {"address_line": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}.
- `branch` (`string`, optional): ID of the associated branch. Example: 5500000050000678.
- `calculator_mode` (`string`, optional): Automatically calculate / correct document values based on the specified calculation mode. Values: initial (Tax-exclusive), total (Tax-inclusive, after discounts), total_pre_discount (Tax-inclusive, before discounts). One of: `initial`, `total`, `total_pre_discount`.
- `client_contact_person` (`string`, optional): The client's contact person, as it will appear on the PDF. Example: John Doe.
- `client_display_name` (`string`, optional): If not provided, the client name will be retrieved from the specified client contact Example: Acme Inc..
- `client_email` (`string`, optional): The client email address, as it will appear on the PDF. Example: john@doe.com.
- `client_phone_number` (`string`, optional): The client phone number, as it will appear on the PDF. Example: 662-222-2222.
- `client_profession` (`string`, optional): The client profession, as it will appear on the PDF. Example: Digital marketing.
- `client_vat_number` (`string`, optional): The client tax ID, as it will appear on the PDF. Example: 123451234.
- `currency_code` (`string`, optional): If not specified, this is set to the contact's default currency code if it exists. In other case the organization's base currency code is used. Example: EUR.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `delivery_notes` (`array`, optional): A list of deliverynote IDs linked to this document. Example: ["4400230020000544"].
- `dispatch_date` (`string`, optional): Date is in the form of YYYY-mm-dd. Example: 2026-11-16.
- `dispatch_time` (`string`, optional): Dispatch time Example: 09:30.
- `documenttype` (`string`, optional): ID of the associated document type. Example: 4400000040000123.
- `draft` (`boolean`, optional): If true the document is considered to be a work in progress. Example: 0.
- `due_days` (`integer`, optional): Days after the issue date, that the invoice will be considered overdue. This affects the document's due date . Use null to not set a due date. Example: 10.
- `exchange_rate` (`string`, optional): Comes into effect when the currency of the transaction is different than the base currency. Will always equal 1.00 for the base currency. Decimal rendered as string, with the . character used as a floating point. Up to 6 decimal places. Example: 1.000000.
- `loading_address` (`object`, optional): The document loading address. Example: {"address_line": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}.
- `move_purpose` (`integer`, optional): Values: 1 (Sale), 2 (Sales on Behalf of Third Parties), 10 (Provision of Ships and Aircraft). One of: `1`, `2`, `10`.
- `number` (`string`, optional): Use empty string or do not send it at all, for automatic numbering. Example: 1001.
- `packages` (`array`, optional): Packages included in the transport. Example: [{"packaging_type": 1, "quantity": 2}].
- `public_notes` (`string`, optional): These notes are displayed on the document's printable form. Example: Notes visible on the invoice.
- `related_documents` (`array`, optional): A list of invoice IDs linked to this document. Example: ["4400230020000543"].
- `related_entities` (`array`, optional): Additional parties involved in the transport. This field applies only to documents that include transport information (i.e., when the is_delivery_note property of the corresponding document type is set to true) Example: [{"contact": "3300000040000100", "contact_display_name": "Acme Inc.", "type": 3}].
- `sequence_flat` (`string`, optional): Sequence Example: A.
- `shipping_address` (`object`, optional): The client shipping address. Example: {"address_line": "4 Catherine St.", "city": "Southaven", "zip": "38671", "country": "US"}.
- `taxes` (`array`, optional): A list of taxes to be applied (optional). If the document contains taxes that have already been applied at the line level, you may optionally resend them here. This will help specify the order that these taxes will have among the other taxes. You may also include additional taxes, which will be calculated based on the total net amount of the document. Example: [{"tax": "6600230050000705"}].
- `template` (`string`, optional): ID of the associated template. Example: 5500000050000999.
- `terms` (`string`, optional): These terms are displayed on the document's printable form. Example: Terms and conditions here.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].
- `vehicle_number` (`string`, optional): Vehicle number Example: ABC-1234.
- `withholding_taxes` (`array`, optional): A list of withholding taxes to be applied. If the document contains withholding taxes that have already been applied at the line level, you may optionally resend them here. This will help specify the order that these taxes will have among the other withholding taxes. Example: [{"tax": "1400230050000705"}].

Example input: `{"client":"<client>","date":"<date>","items":[{"product":"9900000040000600","title":"Pair of socks"}],"organization_id":"<organization_id>"}`

### `elorus_invoice_email`

Email Invoice · Write

Email an Elorus invoice to a recipient, optionally with its PDF attached.
Returns the sent email details.
Use elorus_invoice_get to check the invoice first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `attach_pdf` (`boolean`, required): Whether to include the PDF version of the document as attachment or not. Example: true.
- `bcc` (`array`, required): A list of email addresses to blind carbon-copy the email to. Example: ["accounting@example.com"].
- `cc` (`array`, required): A list of email addresses to carbon-copy the email to. Example: ["accounting@doe.com"].
- `id` (`string`, required): ID of the invoice. Example: 4400000040000123.
- `message` (`string`, required): The email message. May contain html. Example: Hello,<br/>please find the PDF attached..
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `subject` (`string`, required): The email subject.
- `to` (`string`, required): The recipient email address. Example: someone@example.com.
- `attachments` (`array`, optional): A list of invoice attachment IDs to attach in the email Example: ["1050000300010040"].
- `sender_name` (`string`, optional): Sender display name Example: Acme Billing.
- `store_to` (`boolean`, optional): Store the recipient address on the client contact for future use. Example: true.

Example input: `{"attach_pdf":true,"bcc":["accounting@example.com"],"cc":["accounting@doe.com"],"id":"<id>","message":"<message>","organization_id":"<organization_id>","subject":"<subject>","to":"<to>"}`

### `elorus_invoice_email_from_template`

Email Invoice From Template · Write

Email an Elorus invoice using one of the organization's email templates.
Returns the sent email details.
Use elorus_email_templates_list to find a template ID.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): ID of the invoice. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `to` (`string`, required): The recipient email address. Example: someone@example.com.
- `attach_pdf` (`boolean`, optional): Whether to include the PDF version of the document as attachment or not. Example: true.
- `attachments` (`array`, optional): A list of invoice attachment IDs to attach in the email Example: ["1050000300010040"].
- `bcc` (`array`, optional): A list of email addresses to blind carbon-copy the email to. Example: ["accounting@example.com"].
- `cc` (`array`, optional): A list of email addresses to carbon-copy the email to. Example: ["accounting@doe.com"].
- `store_to` (`boolean`, optional): Store the recipient address on the client contact for future use. Example: true.
- `template_id` (`string`, optional): The ID of the email template to render the subject and message from. If omitted, or if it does not match an existing template, the organization's default template for the document's email type is used instead. Example: 5500000050000777.

Example input: `{"id":"<id>","organization_id":"<organization_id>","to":"<to>"}`

### `elorus_invoice_update`

Update Invoice · Write

Update fields of an Elorus invoice (PATCH). Only the fields you send change.
Returns the updated invoice.
Use elorus_invoice_get to read current values; use elorus_invoice_void to void it.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the invoice. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `draft` (`boolean`, optional): If true the document is considered to be a work in progress. Example: 0.
- `exchange_rate` (`string`, optional): Comes into effect when the currency of the transaction is different than the base currency. Will always equal 1.00 for the base currency. This field is read-only while the record is in pending approval status. Decimal rendered as string, with the . character used as a floating point. Up to 6 decimal places. Example: 1.000000.
- `payment_gateways` (`array`, optional): A list of payment gateway IDs that can be used to pay the invoice. Example: ["4400230020000542"].
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_product_create`

Create Product Or Service · Write

Create an Elorus product or service.
Returns the new product or service with its id.
Use elorus_products_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `title` (`string`, required): The product title. Example: Pair of socks.
- `active` (`boolean`, optional): Active Example: 1.
- `barcodes` (`array`, optional): Barcodes associated with the product or service. Example: [{"barcode": "text"}].
- `code` (`string`, optional): Optional product code, up to 40 characters. Example: PS-1.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `description` (`string`, optional): Optional product description. Example: Super-cool expensive socks!.
- `initial_stock` (`array`, optional): Initial stock entries for warehouses. Example: [{"warehouse": "9900000050088867", "stock": "10.00"}].
- `manage` (`boolean`, optional): Whether Elorus should manage the product's stock. Example: true.
- `purchase_taxes` (`array`, optional): A list of tax IDs that should apply by default when purchasing the item. Example: ["6600230050000705"].
- `purchase_value` (`string`, optional): Default unit purchase value (this is not currency-agnostic). Decimal rendered as string, with the . character used as a floating point. Up to 5 decimal places. Example: 30.00.
- `purchases` (`boolean`, optional): Indicates if you purchase this item or not. Example: 1.
- `sale_taxes` (`array`, optional): A list of tax IDs that should apply by default when selling the item. Example: ["6600230050000705"].
- `sale_value` (`string`, optional): Default unit sale value (this is not currency-agnostic). Decimal rendered as string, with the . character used as a floating point. Up to 5 decimal places. Example: 40.00.
- `sales` (`boolean`, optional): Indicates if you sale this item or not. Example: 1.
- `taric_code` (`string`, optional): The TARIC code (TARif Intégré Communautaire; Integrated Tariff of the European Communities) is designed to show the various rules applying to specific products when imported into the EU. Example: 6115950000.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].
- `unit_measure` (`string`, optional): The symbol of the corresponding unit of measurement. You may use the symbol of any custom unit, however the following options are always available: Value Description item Item service Service mm2 Square millimetre cm2 Square centimetre m2 Square metre km2 Square kilometre mm Millimetre cm Centimetre m Metre km Kilometre ml Millilitre l Litre mg Milligram gr Gram kg Kilogram t T... Example: 0. One of: `item`, `service`, `mm2`, `cm2`, `m2`, `km2`, `mm`, `cm`, `m`, `km`, `ml`, `l`, `mg`, `gr`, `kg`, `t`, `minute`, `hour`, `month`, `year`, `man-hour`, `man-day`, `man-month`, `kilowatt-hour`, `package`, `box`, `m3`, `day`.

Example input: `{"organization_id":"<organization_id>","title":"<title>"}`

### `elorus_product_update`

Update Product Or Service · Write

Replace an Elorus product or service's data (PUT): send every field you want to keep, including required ones.
Returns the updated product or service.
Use elorus_product_get to read the current values first.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the product or service. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `title` (`string`, required): The product title. Example: Pair of socks.
- `active` (`boolean`, optional): Active Example: 1.
- `barcodes` (`array`, optional): Barcodes associated with the product or service. Example: [{"barcode": "text"}].
- `code` (`string`, optional): Optional product code, up to 40 characters. Example: PS-1.
- `custom_id` (`string`, optional): Assign a custom ID for easier identification and integration with external systems. This field is optional and can be used to reference records according to your own internal identifiers. Example: ABC-123-a1.
- `description` (`string`, optional): Optional product description. Example: Super-cool expensive socks!.
- `manage` (`boolean`, optional): Whether Elorus should manage the product's stock. Example: true.
- `purchase_taxes` (`array`, optional): A list of tax IDs that should apply by default when purchasing the item. Example: ["6600230050000705"].
- `purchase_value` (`string`, optional): Default unit purchase value (this is not currency-agnostic). Decimal rendered as string, with the . character used as a floating point. Up to 5 decimal places. Example: 30.00.
- `purchases` (`boolean`, optional): Indicates if you purchase this item or not. Example: 1.
- `sale_taxes` (`array`, optional): A list of tax IDs that should apply by default when selling the item. Example: ["6600230050000705"].
- `sale_value` (`string`, optional): Default unit sale value (this is not currency-agnostic). Decimal rendered as string, with the . character used as a floating point. Up to 5 decimal places. Example: 40.00.
- `sales` (`boolean`, optional): Indicates if you sale this item or not. Example: 1.
- `taric_code` (`string`, optional): The TARIC code (TARif Intégré Communautaire; Integrated Tariff of the European Communities) is designed to show the various rules applying to specific products when imported into the EU. Example: 6115950000.
- `trackingcategories` (`array`, optional): An optional list of tracking categories to classify this record. Example: [{"trackingcategory": "7000230020000553", "option": "My custom tag"}].
- `unit_measure` (`string`, optional): The symbol of the corresponding unit of measurement. You may use the symbol of any custom unit, however the following options are always available: Value Description item Item service Service mm2 Square millimetre cm2 Square centimetre m2 Square metre km2 Square kilometre mm Millimetre cm Centimetre m Metre km Kilometre ml Millilitre l Litre mg Milligram gr Gram kg Kilogram t T... Example: 0. One of: `item`, `service`, `mm2`, `cm2`, `m2`, `km2`, `mm`, `cm`, `m`, `km`, `ml`, `l`, `mg`, `gr`, `kg`, `t`, `minute`, `hour`, `month`, `year`, `man-hour`, `man-day`, `man-month`, `kilowatt-hour`, `package`, `box`, `m3`, `day`.

Example input: `{"id":"<id>","organization_id":"<organization_id>","title":"<title>"}`

### `elorus_project_create`

Create Project · Write

Create an Elorus project.
Returns the new project with its id.
Use elorus_projects_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `client` (`string`, required): ID of the associated client. Example: 3300000040000100.
- `members` (`array`, required): A list of the project members. In order to track time for a project, a user must be added to the project member list. Example: [{"member": 1100000040000100, "hourly_rate": "50.00"}].
- `name` (`string`, required): The project name. Example: Web development.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `tasks` (`array`, required): A list of project-specific tasks. These tasks are associated only with this particular project, unlike "global" tasks (which are not included in this list) that can be used across any project. Example: [{"name": "text"}].
- `billing_method` (`string`, optional): The formula used to calculate project revenues based on tracked hours. Values: fixed_cost (Fixed cost), project_rate (Hourly rate), task_rate (Task hourly rate), assignee_rate (Assignee hourly rate), non_billable (Non billable). One of: `fixed_cost`, `project_rate`, `task_rate`, `assignee_rate`, `non_billable`.
- `client_portal` (`string`, optional): Show or hide the project in the client portal. For this setting to take effect, the client must have access to the client portal. Values: all (Show all time entries), billable (Show billable time entries), hide (Hide project). One of: `all`, `billable`, `hide`.
- `description` (`string`, optional): An optional description, used for your own reference. Example: Implementation.
- `fixed_cost` (`string`, optional): A fixed rate for the entire project. Applies only to projects whose billing method is set to "Fixed cost". Decimal rendered as string, with the . character used as a floating point. Up to 2 decimal places. Example: 500.00.
- `hourly_rate` (`string`, optional): The hourly rate of the project. Applies only to projects whose billing method is set to "Hourly rate". Decimal rendered as string, with the . character used as a floating point. Up to 2 decimal places. Example: 50.00.

Example input: `{"client":"<client>","members":[{"member":1100000040000100,"hourly_rate":"50.00"}],"name":"<name>","organization_id":"<organization_id>","tasks":[{"name":"text"}]}`

### `elorus_task_create`

Create Task · Write

Create an Elorus task.
Returns the new task with its id.
Use elorus_tasks_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The task name. Example: Website redesign.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `active` (`boolean`, optional): Instead of deleting, you may archive the record. Example: 1.
- `description` (`string`, optional): The task description. Example: Some text here.
- `hourly_rate` (`string`, optional): The task rate when related project's billing method is "Task hourly rate". Decimal rendered as string, with the . character used as a floating point. Up to 2 decimal places. Example: 50.00.
- `project` (`string`, optional): ID of the associated project. Example: 7700000040000100.

Example input: `{"name":"<name>","organization_id":"<organization_id>"}`

### `elorus_time_entry_create`

Create Time Entry · Write

Create an Elorus time entry.
Returns the new time entry with its id.
Use elorus_time_entries_list to check for an existing record first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `assignee` (`integer`, required): ID of the associated assignee. Example: 1100000040000100.
- `end_datetime` (`string`, required): Timezone information is included. Example: 2026-11-16T11:00:00+02:00.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `start_datetime` (`string`, required): Timezone information is included. Example: 2026-11-16T09:00:00+02:00.
- `billable` (`boolean`, optional): Whether the time entry will be taken into consideration when invoicing the project. Example: true.
- `description` (`string`, optional): An optional description, used for your own reference. Example: Some text here.
- `forcibly_billed` (`boolean`, optional): Indicates that a time entry is forcibly marked as billed, even though it has not been associated with an invoice. Example: true.
- `project` (`string`, optional): ID of the associated project. Example: 7700000040000100.
- `task` (`string`, optional): ID of the associated task. Example: 7800000040000100.
- `user_team` (`string`, optional): ID of the associated user team. When creating new time entries, if this field is not provided, it is automatically populated based on the team the assignee belongs to. Example: 1200000040000100.

Example input: `{"assignee":1100000040000100,"end_datetime":"<end_datetime>","organization_id":"<organization_id>","start_datetime":"<start_datetime>"}`

### `elorus_time_entry_mark_billed`

Mark Time Entry Billed · Write

Mark an Elorus time entry as billed.
Returns the updated time entry.
Use elorus_time_entries_list to find unbilled entries.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the time entry. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_bill_void`

Void Bill · Destructive

Void an Elorus bill, or un-void it with void false.
Returns the bill with its void status.
Voided documents stay on record but no longer count.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the bill (supplier invoice). Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `void` (`boolean`, optional): Whether to void or un-void the document.If not sent, true will be assumed.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_cash_receipt_delete`

Delete Cash Receipt · Destructive

Delete an Elorus cash receipt.
Returns an empty response.
Use elorus_cash_receipts_list to find the ID.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the cash receipt (money received). Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_contact_delete`

Delete Contact · Destructive

Delete an Elorus contact.
Returns an empty response.
Use elorus_contacts_list to find the ID.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the contact (client or supplier). Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_credit_note_void`

Void Credit Note · Destructive

Void an Elorus credit note, or un-void it with void false.
Returns the credit note with its void status.
Voided documents stay on record but no longer count.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the credit note. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `void` (`boolean`, optional): Whether to void or un-void the document.If not sent, true will be assumed.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_estimate_delete`

Delete Estimate · Destructive

Delete an Elorus estimate.
Returns an empty response.
Use elorus_estimates_list to find the ID.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the estimate. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_expense_delete`

Delete Expense · Destructive

Delete an Elorus expense.
Returns an empty response.
Use elorus_expenses_list to find the ID.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the expense. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_invoice_delete`

Delete Invoice · Destructive

Delete an Elorus invoice.
Returns an empty response.
Use elorus_invoices_list to find the ID.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the invoice. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

### `elorus_invoice_void`

Void Invoice · Destructive

Void an Elorus invoice, or un-void it with void false.
Returns the invoice with its void status.
Voided documents stay on record but no longer count.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the invoice. Example: 4400000040000123.
- `organization_id` (`string`, required): ID of the Elorus organization to act on, sent as the X-Elorus-Organization header. Find it in Elorus under Settings > Organization (the ID shown in the API section) or in the web app URL. Example: 1234567890123456.
- `void` (`boolean`, optional): Whether to void or un-void the document.If not sent, true will be assumed.

Example input: `{"id":"<id>","organization_id":"<organization_id>"}`

## Related

Other Accounting & Finance connectors ([all 82](/agentkit/connectors/?category=accounting-finance)):

- [QuickBooks](/agentkit/connectors/quickbooks/): Scalekit connector, OAuth, 117 tools
- [Xero](/agentkit/connectors/xero/): Scalekit connector, OAuth, 94 tools
- [Stripe](/agentkit/connectors/stripe/): Scalekit connector, Access token, 178 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
