List the customers the company invoices
Oldest change first. updated_since narrows the list to what changed at or after an instant. A change is stamped as it is written, in the order changes become visible, so a list followed from the newest updated_at it answered misses nothing and needs no overlap. A change of external_id alone is not such a change.
Authorization
bearerAuth An API key minted by an admin under Settings → Developers. It is bound to one company and has a scope: read, or read_write. A request without one, or with one that is not ours, is answered 401 and metered by its client address (x-rate-limits).
In: header
Query Parameters
How many records a page holds. Default 25, at most 100.
1 <= value <= 100The next_cursor of the page before.
1 <= lengthOnly the record that carries this external id.
1 <= length <= 255Only records changed at or after this ISO 8601 instant. To follow a list, ask from the newest updated_at you were answered: that record comes again, with everything changed after it.
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$date-timeResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/customers"{ "object": "list", "data": [ { "object": "customer", "id": "string", "external_id": "string", "name": "string", "country_key": "string", "is_person": true, "send_method": "email", "street": "string", "zip_code": "string", "city": "string", "phone": "string", "email": "string", "webpage": "string", "att_person": "string", "vat_number": "string", "se_number": "string", "p_number": "string", "ean_number": "string", "use_cvr": true, "company_type_key": "string", "preferred_invoice_language_key": "string", "preferred_invoice_currency_key": "string", "external_reference": "string", "payment_condition_type": "string", "payment_condition_number_of_days": -9007199254740991, "invoice_mail_out_option_key": "string", "payment_mean": "string", "vat_zone_ref": "string", "payment_terms_ref": "string", "layout_ref": "string", "customer_group_ref": "string", "updated_at": "string" } ], "has_more": true, "next_cursor": "string"}Delete a customer DELETE
Refused with `DELETE_BLOCKED_BY_REFERENCES` (409) while an invoice, a recurring series or a credit note of the company names the customer: the platform is then not asked. Refused with `DELETE_BLOCKED_BY_BOOKINGS` (409) when the accounting platform holds bookings against the customer. Either way nothing is deleted.
Read one customer GET
Næste side