Search by

invoiceninja / sdk-php

turbo124hillel369

The Invoice Ninja v5 PHP SDK

Package info

github.com/invoiceninja/sdk-php

pkg:composer/invoiceninja/sdk-php

Statistics

Installs: 64 592

Dependents: 0

Suggesters: 0

Stars: 87

Open Issues: 0

v2.0.0 2026-11-02 01:12 UTC

This package is auto-updated.

Last update: 2026-11-02 01:13:40 UTC


README

Installation

Add the Invoice Ninja SDK

composer require invoiceninja/sdk-php

Setup

use InvoiceNinja\Sdk\InvoiceNinja;
   
$ninja = new InvoiceNinja("your_token");
$invoices = $ninja->invoices->all();
  • To connect to a self hosted version use ->setUrl() on the $ninja object.

Responses and errors

send() and the entity/company JSON methods return arrays decoded from JSON objects or lists. Invalid JSON, scalar/null roots, and unexpected empty responses throw InvoiceNinja\Sdk\Exceptions\ApiException. Integers outside PHP's integer range are decoded as strings to preserve their value.

Successful HEAD requests and empty 204/205 responses return []. A nonempty body on HEAD/204/205 is rejected. Final non-2xx responses throw ApiException even with http_errors=false; this includes redirects that were not followed. The exception code contains the HTTP status, or 0 for a transport failure. Decoder and transport exceptions are retained as previous exceptions.

stream() and download() return the original response bytes as a string, including empty downloads. streamAsObject() and downloadAsStream() return a PSR-7 StreamInterface; use setOptions(['stream' => true]) for HTTP streaming without buffering the full download. Use download() for PDF/ZIP content; bulk('download', ...) is rejected before making a request. Static accessors such as currencies() return arrays and reject missing or non-array collections.

These contracts replace the previous mixed/null behavior. Update direct callers and subclass overrides of send() when upgrading. Array return types validate the response container, not the contents of an entity schema.

Supports

  • Clients
  • Invoices
  • Quotes
  • Products
  • Payments
  • TaxRates
  • Statics
  • Expenses
  • Expense Categories
  • Recurring Invoices
  • Credits
  • Projects
  • Tasks
  • Vendors
  • Companies
  • Subscriptions
  • Purchase Orders
  • Bank Integrations
  • Bank Transactions
  • Client Gateway Tokens
  • Webhooks

Retrieving Models

Retrieve all clients

    $clients = $ninja->clients->all();

You can perform complex filtering on the ->all() method.

Query parameters can be chained together to form complex queries. The current supported values are:

per_page: The number of clients per page you want returned
page: The page number
include: A comma separated list of relations to include ie. contacts,documents,gateway_tokens
balance: A query to return clients with a balance using an operator and value

  • ie ?balance=lt:10 Returns clients with a balance less than 10
  • available operators lt, lte, gt, gte, eq

between_balance: Returns clients with a balance between two values

  • ie ?between_balance=10:20 - Returns clients with a balance between 10 and 20

email: Returns clients with a contacts.email field equal to an email
id_number: Search by id_number
number: Search by number
filter: Search across multiple columns (name, id_number, first_name, last_name, email, custom_value1, custom_value2, custom_value3, custom_value4)
created_at: Search by created at (Unix timestamp)
is_deleted: Search using is_deleted boolean flag

For example,

$clients = $ninja->clients->all([
    'balance' => 'lt:10', // get all clients with a balance less than 10
    'per_page' => 10, // return 10 results per page
    'page' => 2, // paginate to page 2
    'include' => 'documents', // include the documents relationship
]);

Retrieve a client by its primary key.

    $client = $ninja->clients->get("CLIENT_HASHED_ID");

Retrieving an invoice by it's number:

    $client = $ninja->invoices->all(['number' => '0001']);

Inserting & Updating Models

Create a new client

    $client = $ninja->clients->create(['name' => 'A new client']);

Create a new Client with a contact

    $clients = $ninja->clients->create([
        'name' => 'Brand spanking new client',
        'contacts' => [
            [
                'first_name' => 'first',
                'last_name' => 'last',
                'send_email' => true,
                'email' => 'gi-joe@example.com',
            ],

        ]
    ]);
    

Update an existing client

    $client = $ninja->clients->update("CLIENT_HASHED_ID",['name' => 'A client with a updated name']);

Please Note

When updating a client, you must always include the current contacts (array), if no contacts are included, the system will wipe the contacts from the client record.

Create an invoice

    $invoice = $ninja->invoices->create([
        'client_id' => $client_hashed_id,
        'date' => '2022-10-31',
        'due_date' => '2022-12-01',
        'terms' => 'These are your invoice terms.',
        'footer' => 'Invoice footer text',
        'line_items' => [
            [
                'product_key' => 'some_product_key',
                'notes' => 'description',
                'quantity' => 1,
                'cost' => 10
            ],
            [                
                'product_key' => 'another_product_key',
                'notes' => 'description',
                'quantity' => 1,
                'cost' => 10
            ],
        ],
    ]);

When creating an invoice, you can perform actions on the invoice in a single call, for example, say you wish to create an invoice and also apply a payment to the invoice:

    $invoice = $ninja->invoices->create([
        'client_id' => $client_hashed_id,
        'date' => '2022-10-31',
        'due_date' => '2022-12-01',
        'terms' => 'These are your invoice terms.',
        'footer' => 'Invoice footer text',
        'line_items' => [
            [
                'product_key' => 'some_product_key',
                'notes' => 'description',
                'quantity' => 1,
                'cost' => 10
            ],
            [                
                'product_key' => 'another_product_key',
                'notes' => 'description',
                'quantity' => 1,
                'cost' => 10
            ],
        ],
    ], 
    ['paid' => true] //the second parameter in this method is an array of actions ie paid,mark_sent_send_email,auto_bill
);

Or if you wish to apply a partial payment

    $invoice = $ninja->invoices->create(['client_id'=> 'CLIENT_HASHED_ID'], ['amount_paid' => 10]);

Or you may want to automatically send and charge the invoice note requires a payment method on file

    $invoice = $ninja->invoices->create(['client_id'=> 'CLIENT_HASHED_ID'], ['auto_bill' => true, 'send_email' => true]);

Bulk actions

You can perform bulk actions against one or many entities. For example if you wish to batch archive a range of invoice you would do

  $bulk = $ninja->invoices->archive(["hash_1","hash_2"]);

You can access the raw bulk method using the following:

$bulk = $ninja->invoices->bulk("archive", ["hash_1","hash_2"]);

If you wanted to download a invoice PDF

    $pdf = $ninja->invoices->download(["hash_1"]);

The following are a list of available bulk actions for invoices:

  • mark_sent
  • download (use the download() helper)
  • restore
  • archive
  • delete
  • paid
  • clone_to_quote
  • clone_to_invoice
  • cancel
  • reverse
  • email

For more examples of what can be achieved with the SDK, please inspect the tests folder in this repository. If you need clarity or more explicit examples of how to use the SDK, please create a issue.

Development and testing

The SDK and development dependencies support PHP 8.2 and later. The current manifest uses PHPUnit 11, Guzzle 7 or 8, and Carbon 3. CI tests both Guzzle majors on PHP 8.2–8.5.

Install dependencies and run the offline suite:

composer install
composer test-unit

composer test performs a read-only authentication check followed by the offline suite. It does not run the CRUD integration tests or create API data. The bare PHPUnit command defaults to the offline suite as well.

Copy .env.example to .env and set INVOICE_NINJA_TEST_URL and INVOICE_NINJA_TEST_TOKEN. The bootstrap loads .env from the repository root; exported shell/CI variables take precedence. .env is ignored by Git.

composer test-api   # GET /api/v1/ping only; fails immediately on rejection
composer test       # Authentication check, then offline tests
composer test-unit  # Offline tests without contacting the API

Invalid URLs, unreachable APIs, and rejected tokens stop the command. Tests never provision credentials, create accounts, reset databases, or change API state to make authentication succeed.

The legacy integration suite performs CRUD operations. It is disabled unless INVOICE_NINJA_ALLOW_WRITE_TESTS=1 is explicitly set for an authorized disposable API; composer test-integration checks this opt-in before contacting the API. Do not enable it for credential troubleshooting or a shared instance.

Enable PCOV or Xdebug coverage mode, then run:

# With PCOV enabled in the CLI:
composer test-coverage
# With Xdebug installed:
XDEBUG_MODE=coverage composer test-coverage

This runs the read-only authentication check and offline suite, writes coverage/html/index.html and coverage/clover.xml, and enforces 100% executable source line coverage. PHPUnit warnings, notices, deprecations, skipped tests, and incomplete tests fail the run. The coverage check measures line coverage, not branch/path coverage. The offline suite independently covers all executable source lines, so CI can enforce coverage without an API instance.

Pull requests run the PHP/Guzzle compatibility matrix, a lowest-dependency job, locked-dependency coverage, and a security audit. The manually dispatched API job uses the same read-only authentication check and offline coverage commands.

Dependency compatibility notes

Carbon 3 is now required; applications pinned to Carbon 2 must upgrade it. Guzzle 7.16.1+ and 8.3.1+ are supported. Use string header values (or non-empty arrays of strings) and associative arrays for nested form data, such as group settings, for compatibility with Guzzle 8. Request methods are normalized to uppercase consistently across both Guzzle majors.