# Your systems work with VITT through the API.

> Your shop, CRM or warehouse tool works directly with VITT through a REST API: it creates partners and products, issues invoices and sends them to e-Factura, reads received invoices and learns from webhooks what changed. AI assistants such as Claude or ChatGPT connect separately, over MCP.

Source: https://vitt.ro/en/integrations/api-mcp/

- **Docs in English and Romanian.** Guides, every error explained and the full API reference, at docs.vitt.ro.
- **An OpenAPI 3.1 contract.** API v1 is described in OpenAPI 3.1, from which you can generate your client.
- **Reference data.** Document series, VAT rates, units of measure and the company's details, read straight from VITT.

## Invoices issued from your system, sent to e-Factura.

An invoice created through the API passes the same checks as in the app: it is issued with its PDF and XML and goes to ANAF like any other.

- **Partners and products.** List, read, create, update and archive them. Add a Romanian company by its CUI, from ANAF's data, or an EU one through VIES.
- **Invoices, from draft to ANAF.** Drafts, issuing, credit notes, sending to e-Factura, PDF and XML, with the payment state and ANAF's answer.
- **Received invoices.** Read your suppliers' invoices, from SPV, uploads or receipts, with their PDF, XML and attachments.
- **Retries without duplicates.** With an idempotency key, a request repeated after a network error takes effect once.

## Each key does only what you allowed.

API keys belong to the company and are created in Settings › Integrations › API. An admin chooses what each key may read and write.

- **Permissions per key.** The shop's key can issue invoices, while a reporting key only reads.
- **The key belongs to the company.** The integration does not depend on a colleague's account: the key stays the company's, with its permissions.

## Know straight away what changed.

VITT tells your system through webhooks: an invoice issued, accepted or rejected by ANAF, a payment, a received invoice, a partner or product created or changed.

- **Signed.** Every delivery is signed to the Standard Webhooks scheme, so your system can check it comes from VITT.
- **Nothing lost.** After downtime, read the events you missed from the events feed, in order.

## Claude and ChatGPT connect over MCP.

For AI assistants, VITT runs an MCP server. An assistant searches invoices, prepares drafts and reads balances, reports and stock, with the capabilities an admin grants each connection.

- **API or MCP.** The API is for your company's systems, which can issue invoices and send them to ANAF. An AI assistant cannot approve an invoice or send it to ANAF.
- **Approval in VITT.** Invoices created or edited from an assistant wait for approval in VITT by default.
- **What the assistant sees.** The company chooses how much partner data an assistant sees, and a new connection starts with no access.

What an assistant reads reaches its provider (such as Anthropic or OpenAI), under your company's own terms with that provider.

## For developers

The API documentation, with getting-started guides, an explanation of every error and the full reference, is at [docs.vitt.ro](https://docs.vitt.ro), in English and Romanian. The API follows the same rules as the app: an invoice issued through the API is validated for e-Factura like any other in [invoicing](/en/features/invoicing-e-factura/).

## For AI assistants

To work with VITT from Claude, ChatGPT or another assistant, you do not need the API: connect over MCP, with sign-in and capabilities an admin grants. Everything an assistant can do is on the [VITT in Claude and ChatGPT](/en/features/claude-chatgpt-mcp/) page.

## FAQ

### What is the VITT API for?

For your company's systems: a shop, a CRM, a warehouse tool. Through the API they create partners and products, issue invoices and send them to e-Factura, and read received invoices.

### Where is the API documentation?

At docs.vitt.ro, in English and Romanian: guides, every error explained and the full reference, generated from the OpenAPI contract.

### Can the API send invoices to ANAF?

Yes, if the key has that permission. An API key is your company's own system, acting on its behalf. An AI assistant connected over MCP cannot do this.

### How do I know when ANAF accepts or rejects an invoice?

Through webhooks: VITT sends an event when an invoice is issued, accepted or rejected by ANAF, and when its payment state changes.

### What is the difference between the API and MCP?

The REST API is for software, with company keys and permissions per key. MCP is for AI assistants such as Claude or ChatGPT, with capabilities an admin grants per connection and approval in VITT for invoices.
