Runs the reqBodySchema or reqQueryParametersSchema of a custom API on some data and answers the errors the API would refuse it with, without running the API.
Method
POST
URL
/api/system-api/admin/is-valid-data-for-custom-api : admin is the user path of your account
Body
{ name, type, data } or an array of them
Answer
data : an array of errors (empty when valid), or an array of arrays
{"success":true,"statusCode":200,"data":[{"type":"required","field":"first_name","message":"Please provide valid 'first_name' field with type 'string'.","code":400},{"type":"min","field":"phone","message":"Please provide minimum '5' for 'phone' field.","code":400}]}
Key
Meaning
name
The name of the custom API.
type
BODY for reqBodySchema, QUERY_PARAMS for reqQueryParametersSchema.
Over HTTP, a system API answers once its settings give it apiAccessType: TOKEN_ACCESS (the token of an API user whose group grants this system API, in x-am-authorization) or IS_PUBLIC. Without settings it is NO_ACCESS : your code calls it through g.sys, the admin panel tests it, and an HTTP call is refused.
The settings can also cache the answer or require person tokens (authProviders) ; pre and post hooks run around it like around any API.
The request headers apply : x-am-response-case, x-am-content-type-response, x-am-internationalization, x-am-tenant-username…