Read one explicit page of Invoice Ninja v5 product summaries or a known product by opaque hashed ID. Uses your company API token and root public HTTPS site. No client, invoice/payment records, rich notes, custom values, relationships, documents, writes, polling, automatic paging/retries or managed OAuth. Root-site HTTPS installations only.
What you can do (2)
What you can do
Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List products — invoiceninja.products.list |
Read |
Get a product — invoiceninja.products.get |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Invoice Ninja, then enter the issued values in the connection form below.
- In your Invoice Ninja v5 company, open Settings > Account Management > Integrations > API tokens and create/copy a token for this connection. Enter your root HTTPS site URL (https://invoicing.co for the hosted product, or your public self-hosted root URL) into Invoice Ninja HTTPS site URL and the token into Invoice Ninja API token. Root-site HTTPS installs are supported; private-network, nonstandard-port and subdirectory installs are outside this subset. Use your own company token, not an account password or v4 X-Ninja-Token. The v5 API uses X-API-TOKEN and X-Requested-With: XMLHttpRequest headers; the API_SECRET setting only applies to the separate login route and is not requested here. Save, select product reads and use your Tooluse.net API key to call explicit page examples, then copy an opaque hashed product ID into the get example. Cost/price values follow the company product configuration, not invoice totals or currency conversion. No client/payment/invoice records, notes, relationships, writes, automatic pagination/retries, plan provisioning or managed OAuth.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Invoice Ninja HTTPS site URL | Required |
| Invoice Ninja API token | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"page": 1,
"per_page": 20
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
List products — invoiceninja.products.list
Read one explicit page of Invoice Ninja v5 product summaries. Returns opaque IDs, product keys, cost/price values and lifecycle metadata; omits notes, relationships, custom values and documents. Prices use the company’s configuration; this is not an invoice total or currency conversion.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.page |
integer | Required | Explicit page number. | minimum: 1; maximum: 1000000000 |
query.per_page |
integer | Required | Requested records per page; this adapter bounds the page to 100. | minimum: 1; maximum: 100 |
Full JSON Schema
Example input
{
"query": {
"page": 1,
"per_page": 20
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Get a product — invoiceninja.products.get
Read one Invoice Ninja v5 product summary using its opaque hashed product ID. Omits rich notes, relationships, custom values and documents. Does not read invoices, clients or payments.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.product_id |
string | Required | Opaque hashed product ID from the product list; not a v4 numeric ID. | minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9_-]+$" |
Full JSON Schema
Example input
{
"path": {
"product_id": "Opnel5aKBz"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.