model
Try a change: what goes with supposing claims do not hold, or numbers take values
Read-only, and kept nowhere: for each accepted claim supposed not to hold, what rests on it and each option’s answer that loses its footing; for each number at a value, which side of each threshold on it the value falls, beside where the accepted ranges are now. It reads no view, and compares no option with another.
post/workspaces/{id}/questions/{questionId}/suppose
Request
- Base URL: https://api.swingfactor.ai/v1
- URL: https://api.swingfactor.ai/v1/workspaces/{id}/questions/{questionId}/suppose
- Auth: HTTP bearer
Path parameters
idstring uuid required
The workspace's id (a UUID).
questionIdstring uuid required
The question's id (a UUID).
Request body
Response
What goes with it.
Changes
No recorded changes to this operation across all 1 revision of this API.