mobileSignupBuiltInFieldRules
Public: no authentication required.
Lists whether the Sign Up form hides, offers or requires each built-in field (trading name, tax ID, registration number, secondary contact), before any session exists. The organization comes from the build's subdomain, as for mobileRegisterBuyer.
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
- cURL
query MobileSignupBuiltInFieldRules {
mobileSignupBuiltInFieldRules {
defaultRule
field
rule
surface
}
}
curl -X POST "https://<api-host>/graphql" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $ACCESS_TOKEN" \
--data @- <<'EOF'
{
"query": "query MobileSignupBuiltInFieldRules {\n mobileSignupBuiltInFieldRules {\n defaultRule\n field\n rule\n surface\n }\n}"
}
EOF
Response:
{
"data": {
"mobileSignupBuiltInFieldRules": [
{
"defaultRule": "string",
"field": "string",
"rule": "string",
"surface": "string"
}
]
}
}
mobileSignupBuiltInFieldRules(
subdomain: String
): [BuiltInFieldRule!]!
Arguments
mobileSignupBuiltInFieldRules.subdomain ● String scalar
The tenant subdomain baked into this buyer-app build.
Type
BuiltInFieldRule object
Whether one built-in field is hidden, optional or required on one form.