createCorporateCustomer

mutation · in the family Corporate customer

What it does

Create a new corporate customer — a business buyer with house terms at your organization.

Create a CorporateCustomer in the caller's org group; requires the unrestricted capability.

Who may call it

Capability area: Pricing — Prices, price schedules, promotions, coupons and the money rules of selling.

• Owner
• Manager
• An API key whose scope allows api:createCorporateCustomer

Arguments

Returns

CorporateCustomer CorporateCustomer! — A CorporateCustomer — WHO the merchant SELLS TO on business terms: the shared B2B customer MASTER, the sell-side mirror of the Vendor supplier master. Group-parented + deliberately thin (caption = the trading name · legalName · taxId · code): contact data + buyers ride the Contact/ContactAssignment family (a CorporateCustomer is an assignment HOST — buyers are purchasing-buyer-role assignments); the org-specific commercial payload (terms · credit · price group · addresses) IS the OrgCustomer relationship (an active OrgCustomer = the B2B selling enablement — the OrgVendor mirror). SEARCHABLE (a customer book you can't search by name fails its purpose — the law). Doom is blocked by NON-doomed OrgCustomer selections and LIVE hosted ContactAssignments; open ORDERS naming the customer never block — order refs re-validate FRESH at place. NOT an identity class (buyer auth/portal is); the customer hierarchy (parent company) is a NAMED deferral.

Example request

mutation ExampleCreateCorporateCustomer($input: NewCorporateCustomerInput!) {
  createCorporateCustomer(input: $input) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    legalName
    taxId
    code
  }
}

Variables:

{
  "input": {
    "caption": "Blue jeans"
  }
}

Send it with the envelope naming the version: "extensions": {"at": {"version": {"name":"genesis","number":0}}}.

Example response

{
  "data": {
    "createCorporateCustomer": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "CU-EXMP-0000-000F",
      "type": "CorporateCustomer",
      "caption": "Blue jeans",
      "status": "active",
      "parentId": "01900000-0000-7000-8000-065235280000",
      "rootId": "01900000-0000-7000-8000-a093dd800000",
      "createdAt": "2027-01-31T00:00:00.000Z",
      "updatedAt": "2027-01-31T00:00:00.000Z",
      "revisionNum": 1,
      "revision": "01900000-0000-7000-8000-b7960e180000",
      "legalName": "Blue jeans",
      "taxId": "<tax id>",
      "code": "BJ-001"
    }
  },
  "extensions": {
    "at": {
      "callId": "01EXAMPLE-CALL-ID",
      "version": {
        "requested": {
          "name": "genesis",
          "number": 0
        },
        "serviced": {
          "name": "genesis",
          "number": 0
        }
      }
    }
  }
}

Errors this call can answer

• VALIDATION/INVALID — Something in the request is not valid. (VALIDATION)
• AUTHN/REQUIRED — Sign in to do this. (AUTHN)
• AUTHZ/FORBIDDEN — Your role does not allow this action. (AUTHZ)
• RATE_LIMIT/THROTTLED — Too many requests in a short time. (RATE_LIMIT)
• CONFLICT/* — The record’s state, or a change made in the meantime, does not allow this; the codes are on the CONFLICT page. (CONFLICT)
• VALIDATION/VERSION_REQUIRED — The request did not say which app version it came from. (VALIDATION)

Dry run

Add dryRun: true to the request envelope (extensions.at) to rehearse this call: every check runs, the write is rehearsed against the current records and nothing is stored; the answer is the refusal a real call would give, or the record it would create. Every response to a rehearsal carries dryRun: true, so a rehearsed record is never mistaken for a saved one.

Used in

• Open an account for a business customer