JouloDocs

Attach a charger to a customer who already activated

For a customer who already activated and gets a second charger, a replacement, or a charger the claim could not link. One draft names one charger, so POST /partner/customers refuses that customer as already_drafted. Name the customer with customer_ref from GET /partner/customers, not with your own external_ref. Without charger_brand, or with bluebird: we check the charger with BlueBird, link it to the customer's account and fetch its sessions back to 1 January 2026. With push: only for a partner that Joulo enabled to deliver sessions itself. We attach your charge point with the details you send, as at upload, and from then on POST /partner/sessions accepts its sessions. Send the history since 1 January 2026 after the attach. The customer signs nothing new: the registration and the authorization belong to the account and its EAN. Attribution and fees do not change. For a BlueBird replacement, disable the old charger first with POST /partner/chargers/disable, then attach the new one. A charger that had another owner books nothing from before its hand-over. Idempotent per charger: a second call returns already_attached: true and changes nothing. After a BlueBird attach, POST /partner/chargers/disable works for this charger too.

POST
/partner/customers/chargers
AuthorizationBearer <token>

Partner API key, sent as Authorization: Bearer <key>. Production keys start with jpk_live_ and work only on https://api.joulo.nl. Sandbox keys start with jpk_test_ and work only on https://api-staging.joulo.nl. Sandbox keys minted before September 2026 also start with jpk_live_. A key used on the wrong host returns 401 with a detail. A key is bound to one partner and reaches only the Partner API routes. Any other route returns 404 when it does not exist. A route that needs a scope the key lacks, such as GET /sessions, returns 403 with error: Insufficient scope and a required_scope. Every other route returns 403 with error: partner_api_key_scope. Mint and revoke keys in the partner portal. A partner has one active key at a time.

In: header

customer_refstring

Joulo's 8-character reference for the customer, from GET /partner/customers or GET /partner/ere-positions. Not your own external_ref.

Match^[0-9a-f]{8}$
charger_idstring

With bluebird: the BlueBird charger id. Any usual spelling of the MAC address works. With push: your own charge point id, kept as sent, at most 120 characters. Send the same id with every session.

charger_brand?string

Where Joulo gets the charger's sessions. bluebird (the default): Joulo reads them from BlueBird Power. push: you deliver them yourself to POST /partner/sessions. Only a partner that Joulo enabled for that may send push.

Default"bluebird"
Value in"bluebird" | "push"
charger_vendor?string

Push partners only: chargePointVendor from the charger's BootNotification. With charger_model it decides the catalog model, and so whether the charger has a MID meter.

charger_model?string

Push partners only: chargePointModel from the charger's BootNotification.

charger_serial?string

Push partners only: the charger's serial number. A serial already on a Joulo laadstation is rejected with serial_in_use, because the charger would reach us twice.

charger_meter_type?string

Push partners only: meterType from the charger's BootNotification. For a Vestel or Alp EV that reports EVC04 or EVC10, it decides whether the charger has a MID meter: MID with a numeric charger_meter_serial means yes, internal means no. Anything else goes to a manual MID review.

charger_meter_serial?string

Push partners only: meterSerialNumber from the charger's BootNotification. A MID meter type counts only with a numeric serial of 6 to 12 digits.

charger_location?PartnerChargerLocation

Push partners only: the address of the charge point. Joulo compares it with the address of the EAN (eis C2). A mismatch never refuses the row: Joulo reviews it. Postcode and house number are required when you send the object; street and city are optional. Without them Joulo ignores the object and says so in chargers[].location. The customer is never rejected for it.

Response Body

curl -X POST "https://api.joulo.nl/functions/v1/api/partner/customers/chargers" \  -H "Content-Type: application/json" \  -d '{    "customer_ref": "3f9a1c07",    "charger_id": "ec:64:c9:6d:29:40"  }'

{
  "ok": true,
  "charger_id": "ec:64:c9:6d:29:40",
  "already_attached": false,
  "attached_at": "2026-11-10T09:12:31.204118+00:00"
}

{
  "error": "customer_ref_required",
  "detail": "customer_ref must be the 8-character reference from GET /partner/customers."
}
{
  "error": "Missing or invalid API token"
}
{
  "error": "session_push_not_enabled",
  "detail": "This partner does not deliver sessions itself. Contact Joulo."
}
{
  "error": "customer_not_found",
  "detail": "No customer of yours with this customer_ref."
}
{
  "error": "charger_claimed",
  "detail": "Another customer holds this charger. Disable it there first with POST /partner/chargers/disable."
}
{
  "error": "charger_not_linked",
  "detail": "BlueBird does not list this charger for the Joulo operator account. Link it to Joulo in BlueBird first."
}
{
  "error": "Too many requests",
  "retry_after_seconds": 3
}
{
  "error": "attach_failed",
  "detail": "We could not attach the charger. Send the same request again: it is idempotent."
}
{
  "error": "bluebird_unavailable",
  "detail": "We could not check the charger with BlueBird. Send the same request again: it is idempotent."
}