# Billit integrations: orders, payments and parties

> Create an order, add a payment to an order and create a party in Billit, and start a workflow when Billit sends “Order created”.

**Canonical page:** https://tray.ai/connectors/billit-integrations/
**Categories:** Finance
**Connects through:** HTTP Connector

## Overview

Billit is Belgian invoicing and accounting software for sending and receiving e-invoices over Peppol, tracking payments, and managing customers, suppliers and products. Tray.ai connects to Billit through the HTTP Connector, so your workflows can call the Billit API alongside the rest of your stack.

## Use cases

### Orders

Read, create, update, and delete orders in Billit from any Tray.ai workflow. The Billit API covers calls such as list orders and get an order.

- List orders
- Get an order
- Create an order

### Payments

Read and create payments in Billit from any Tray.ai workflow. The Billit API covers calls such as add a payment to an order and list financial transactions.

- Add a payment to an order
- List financial transactions

### Parties

Read, create, and update parties in Billit from any Tray.ai workflow. The Billit API covers calls such as list parties and get a party.

- List parties
- Get a party
- Create a party

### Products

Read and create products in Billit from any Tray.ai workflow. The Billit API covers calls such as list products and get a product.

- List products
- Get a product
- Create a product

### Documents

Read and create documents in Billit from any Tray.ai workflow. The Billit API covers calls such as list documents and get a document.

- List documents
- Get a document
- Save a document

### Webhooks

Read, create, delete, and manage webhooks in Billit from any Tray.ai workflow. The Billit API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- Delete a webhook

## Challenges Tray.ai solves

### Keeping Billit credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Billit credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Billit API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Billit API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Billit?

Yes. Tray.ai connects to Billit through the HTTP Connector, which calls the Billit API directly. Any call the Billit API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Billit?

The Billit API uses an API key in a request header and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Billit connector?

Billit runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Billit connector from the Billit API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/