Views
POST /workspace/{workspaceId}/views/validate
Changed onCheck a new view without creating it.
Runs every check a create runs and answers with the view as it would be stored, or the same 422 a create would give. Nothing is saved. An agent asks a person to confirm a view before saving it; when the API refused the view only afterwards — a hierarchy level or quarter the workspace does not have — the person saw an error on a card they had just approved. A separate route rather than a flag on the create: an API that predates it answers 404, never a real create.
Request
- Base URLhttps://api.craft.io
- URLhttps://api.craft.io/workspace/{workspaceId}/views/validate
- AuthAPI key in header x-api-key
Path parameters
workspaceIdstring required
Request body
Response
The view as it would be created
Changes
- info
endpoint added
- info