Invoicecave

API keys and the REST API

Create, use and look after API keys, and build your own integration against the REST API.

IBy the Invoicecave team · Updated September 18, 2026

If you would rather write code than talk to an assistant, InvoiceCave has a REST API. It powers the same operations the MCP tools expose.

API keys

Create keys in Settings. A key looks like `ic_...` and is shown to you once.

How many you get depends on your plan: 1 on Free, 3 on Pro, unlimited on Enterprise. Multiple keys are useful so you can give each integration its own and revoke one without breaking the others.

Using a key

Send it as a bearer token:

``` Authorization: Bearer ic_your_api_key ```

Looking after keys

A key can do anything your account can do — create invoices, read customer data, record payments. Treat it accordingly:

  • Never commit one to a git repository.
  • Never put one in front-end code, where anyone can read it.
  • Keep it in an environment variable or a secrets manager.
  • Use a separate key per integration.
  • Revoke immediately if a key is exposed, and issue a new one. Revoking is instant.

If a key does leak, revoking it is the fix — you do not need to change anything else about your account.

Rate limits

Requests are rate limited to keep the service stable for everyone. Handle a `429` response by backing off and retrying rather than hammering, and your integration will be fine.

Documentation

Full endpoint reference at invoicecave.com/docs. The MCP manifest at /api/mcp/manifest is public and the tool schemas are self-describing, so you can discover what is available programmatically.

API or MCP?

Use the REST API when you are building software — a website, a billing integration, an internal system.

Use MCP when a person wants to do the work by asking rather than clicking. See [Connect InvoiceCave to Claude](/help).