Integration

Invoicing.plus integration

Invoicing.plus is a French invoicing and sales management service. An agent can list, read and create customers, products, estimates and orders, create, edit, validate and e-mail invoices (with PDF download), record and delete payments, manage payment methods, tax rates, units and projects, and add leads. Every business call names the company it acts on in the X-Company parameter: get the id from list_companies first. Not exposed: contacts, pre-billing, recurring invoices and purchase (supplier) invoices, whose responses the vendor does not document, company and administrator creation, and token management; customers' registration and VAT numbers and postal addresses, and project locations and photos, are not returned. Authentication: a personal Bearer token, which the account holder generates once from the vendor's token request with the account e-mail and password (it can be run from the vendor's interactive API reference), leaving the short-lived option off; it represents that user and only reaches the companies and operations the user is allowed. Limit: 240 requests per minute per user, shared across companies; over it the API answers 429 with Retry-After.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Invoicing.plus.Built from the 53 Invoicing.plus tools below, on the connection you add once.

What you can do with Invoicing.plus

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Invoice, 7 operations

  • create_invoiceCreate invoicePOSTCreates a DRAFT invoice (or credit note with refund=true) for a customer for real. Needs customer_id and lines; validate_invoice then makes it final.
  • delete_invoiceDelete invoiceDELETEDeletes a DRAFT invoice for real. Validated invoices are not deleted even though the call answers 200: read it again with get_invoice to check.
  • get_invoiceGet invoiceGETReturns one invoice: customer, dates, number, status, payment status, refund, deposit and final flags, totals and lines.
  • list_invoicesList invoicesGETLists invoices with customer id, dates, number, status, payment status (UNPAID, PARTIALLY_PAID, PAID), totals and lines, paginated.
  • send_invoiceSend invoicePOSTE-mails an invoice for real to the address in to, with your subject, sender name and sender address. The e-mail goes out immediately.
  • update_invoiceUpdate invoicePUTChanges a DRAFT invoice (a validated one returns 404). Without lines the stored lines stay; with lines all lines are replaced and totals recalculated.
  • validate_invoiceValidate invoicePOSTValidates a draft invoice for real; it then can no longer be edited or deleted through this API. On plans with an approved e-invoicing platform, validated invoices are transmitted automatically.

Item, 5 operations

  • create_itemCreate itemPOSTCreates a product or service for real. Only name is required; give price, default_tax_id and unit_id as needed.
  • delete_itemDelete itemDELETEDeletes a product or service for real.
  • get_itemGet itemGETReturns one product or service by id: name, description, code, account code, price, eco-tax, default tax rate and unit.
  • list_itemsList itemsGETLists the company's products and services with code, price, default tax rate and unit (ids and names). Use the ids when building document lines.
  • update_itemUpdate itemPUTChanges a product or service; send only the fields to change.

Customer, 4 operations

  • create_customerCreate customerPOSTCreates a customer in the company for real. Only name is required; returns the new customer's id.
  • delete_customerDelete customerDELETEDeletes a customer for real.
  • get_customerGet customerGETReturns one customer by id: name, company name, code, account code, e-mail and phone.
  • list_customersList customersGETLists the company's customers (id, name, code, account code, e-mail, phone), paginated. Filter by status active or inactive, or search by name or document reference.

Payment, 4 operations

  • create_paymentCreate paymentPOSTRecords a payment for real on an invoice (invoice_id) or a credit note (refund_invoice_id). Without amount the remaining balance is used; it may not exceed the balance.
  • delete_paymentDelete paymentDELETEDeletes a recorded payment for real.
  • get_paymentGet paymentGETReturns one payment by id.
  • list_paymentsList paymentsGETLists payments recorded in the company: number, date, amount, customer, invoice or credit note, payment method and notes.

Payment method, 4 operations

  • create_payment_methodCreate payment methodPOSTCreates a payment method for real; the name must be unique in the company.
  • delete_payment_methodDelete payment methodDELETEDeletes a payment method for real; refused with 403 when payments or expenses use it.
  • get_payment_methodGet payment methodGETReturns one payment method by id.
  • list_payment_methodsList payment methodsGETLists the company's payment methods (id, name, accounting code).

Project, 4 operations

  • create_projectCreate projectPOSTCreates a project for real.
  • delete_projectDelete projectDELETEDeletes a project for real.
  • get_projectGet projectGETReturns one project by id (name, description, status).
  • list_projectsList projectsGETLists the company's projects (id, name, description, status), paginated; search filters the name.

Estimate, 3 operations

  • create_estimateCreate estimatePOSTCreates an estimate for a customer for real, from product lines. Needs customer_id (from list_customers) and lines. The response is not documented: find the new estimate with list_estimates.
  • get_estimateGet estimateGETReturns one estimate with its customer, dates, number, status, totals and lines (products, quantities, prices, tax).
  • list_estimatesList estimatesGETLists estimates (DEV numbers) with customer, dates, status, totals and lines, paginated. For a full sync use status=ALL and read every page.

Tax type, 3 operations

  • create_tax_typeCreate tax typePOSTCreates a tax (VAT) rate for real.
  • list_tax_typesList tax typesGETLists the company's tax (VAT) rates, whose ids go in default_tax_id and tax_type_id. The vendor does not document the response fields, so it is returned as is.
  • update_tax_typeUpdate tax typePUTChanges a tax (VAT) rate; send only the fields to change.

Code, 2 operations

  • find_customer_by_codeFind customer by codeGETFinds a customer by its customer code. Unknown code returns 404.
  • find_item_by_codeFind item by codeGETFinds a product by its product code. Unknown code returns 404.

Company, 2 operations

  • get_companyGet companyGETReturns the selected company's details (name, legal name, group, logo, colour, the user's admin flag and permissions).
  • list_companiesList companiesGETLists the companies the token's user can access, with the id to pass as X-Company on every other tool, and whether the user is an admin there.

Effortless, 2 operations

  • create_estimate_by_emailCreate estimate by emailPOSTCreates an estimate for real, matching the customer by e-mail and products by code (missing ones are created). The response is not documented: find it with list_estimates.
  • create_invoice_by_emailCreate invoice by emailPOSTCreates a DRAFT invoice for real, matching the customer by e-mail and products by product code; a missing customer or product is created.

Order, 2 operations

  • get_orderGet orderGETReturns one order with customer, dates, number (estimate_number), status, totals, lines and the estimate it came from.
  • list_ordersList ordersGETLists orders (COM numbers; the number is in estimate_number), paginated. By default only DRAFT and PARTIAL_INVOICED; use status=ALL for every status.

Pdf, 2 operations

  • get_estimate_pdfGet estimate pdfGETDownloads the PDF of an estimate as a file.
  • get_invoice_pdfGet invoice pdfGETDownloads the PDF of an invoice as a file.

Unit, 2 operations

  • create_unitCreate unitPOSTCreates a unit for real.
  • list_unitsList unitsGETLists the company's units (hour, flat rate and so on), whose ids go in unit_id. The vendor does not document the response fields, so it is returned as is.

Account code, 1 operation

  • find_customer_by_account_codeFind customer by account codeGETFinds a customer by its accounting code. Unknown code returns 404.

Artisan, 1 operation

  • list_artisansList artisansGETLists the company's artisans (tradespeople records: id, name, code, e-mail, phone), paginated; web and vintage records are excluded.

Company group, 1 operation

  • get_company_groupGet company groupGETReturns the partner group of the authenticated user (id, name, price_child), for partner accounts that manage several companies.

Email, 1 operation

  • find_customer_by_emailFind customer by emailGETFinds a customer by e-mail address. Unknown address returns 404.

Lead, 1 operation

  • create_leadCreate leadPOSTCreates a lead (prospect) for real. The lead's name is taken from company_name and name sets the contact name; super_name is required.

Name, 1 operation

  • find_item_by_nameFind item by nameGETFinds a product by its name. Unknown name returns 404.

Who i am, 1 operation

  • get_current_userGet current userGETReturns the user the token belongs to: id, name, e-mail, phone and language. Needs no company.

Use Invoicing.plus from Claude Code, Cursor or Codex

Connect Invoicing.plus in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Invoicing.plus operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Invoicing.plus

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Invoicing.plus once

    Add your Invoicing.plus connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Invoicing.plus integration FAQ

What can you do with the Invoicing.plus integration?

LiveContext exposes 53 operations on Invoicing.plus, covering invoice, item, customer and payment.

Popular integrations

Browse the whole catalog