customerSignupBuiltInFieldRules

Public: no authentication required.

Lists whether the portal's Request a trade account form hides, offers or requires each built-in field (trading name, tax ID, registration number, address contact and delivery notes, secondary contact), before any session exists. The organization comes from the request host.

Errors: a failed call returns a GraphQL errors entry, not a field on the result, and data may be null or partial. Read the entry's extensions.code and message; every shape and code is in the Error reference.

Example:

GraphQL

query CustomerSignupBuiltInFieldRules {
  customerSignupBuiltInFieldRules {
    defaultRule
    field
    rule
    surface
  }
}

cURL

curl -X POST "https://<api-host>/graphql" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  --data @- <<'EOF'
{
  "query": "query CustomerSignupBuiltInFieldRules {\n  customerSignupBuiltInFieldRules {\n    defaultRule\n    field\n    rule\n    surface\n  }\n}"
}
EOF

Response:

{
  "data": {
    "customerSignupBuiltInFieldRules": [
      {
        "defaultRule": "string",
        "field": "string",
        "rule": "string",
        "surface": "string"
      }
    ]
  }
}

customerSignupBuiltInFieldRules(
  subdomain: String
): [BuiltInFieldRule!]!

Arguments

customerSignupBuiltInFieldRules.subdomain ● String scalar

The portal's subdomain. A fallback for local development only: the request host wins.

Type

BuiltInFieldRule object

Whether one built-in field is hidden, optional or required on one form.