Customer (Account) Endpoints

Operations

Scoping And Permissions

The customer/account is the top-level account record. These endpoints expose only a safe profile projection and enforce strict permission scoping.

• Read (Get, GetByAccountId): any authenticated user may read accounts in their allowed set — their own account (CustomerCode claim) plus any bill-to accounts listed in AdditionalWebAccess. Master contacts may read any account. Sensitive fields (payment/PaySimple ids, credit-card surcharge and GL fields, finance/credit terms, internal AR/ops comments, salesman/branch codes, raw option blobs) are never returned.
• Create: account Administrator only. Deeper provisioning (payment profiles, GUEST-template defaults, initial contacts) is handled by the Registration flow, not this endpoint.
• Update: account Administrator on accounts in the caller's allowed set, or master contacts on any account. Only editable profile fields are changed; financial, payment, billing-terms, and internal accounting fields are never modified.

A Note On accountId

The source ticket references lookup by accountId. There is no separate accountId column on the Customer table today, so accountId aliases the customer code (Code, the primary key). GetByAccountId therefore behaves identically to Get.