Update an individual customer

put

https://app.pennylane.com/api/external/v2/individual_customers/{id}

This endpoint returns the updated individual customer.

This endpoint requires the following scope: customers:all

Path Params

string

required

Individual customer identifier

Query Params

use_2026_api_changes

boolean

Defaults to true

If you are already using the X-Use-2026-API-Changes header, you can ignore this parameter.

The Pennylane API is introducing important changes, which will be rolled out in three phases: preview, sunset and cleanup.

For new user, please use this parameter with true value to opt in directly to the new version of the API.

Preview phase: From January 14th to April 7th 2026. Opt in by setting this attribute to true to test and migrate to the new behavior.

Sunset phase: From April 8th to June 30th 2026. The new behavior becomes the default. Set this attribute to false if you need additional time to migrate.

Cleanup phase: Starting July 1st 2026 The old behavior will no longer be available. You must have migrated by this point.

For more details, see our API documentation https://pennylane.readme.io/docs/2026-api-changes-guide for migration instructions.

Body Params

first_name

string

last_name

string

phone

string

billing_address

object

delivery_address

object | null

payment_conditions

string

enum

Note that the custom option is only used on Pennylane's web app to avoid pre-filling the deadline when creating an invoice. On the API it has no effect and you will still have to provide a deadline when creating an invoice.

billing_iban

string | null

recipient

string

reference

string | null

notes

string | null

emails

array of strings

emails

external_reference

string

The unique external reference assigned to this customer, assigned on creation either by you or Pennylane.

billing_language

string

enum

The language in which the customer will receive invoices. Default is fr_FR

Allowed:

Responses

200Returns the updated individual customer

400Bad request

401Access token is missing or invalid

403Access to this resource forbidden

404The resource was not found

409Conflict with the current state of the target resource, such as when trying to create a resource that already exists.

422Unprocessable content