Compile Ontology Request
POST/api/v1/ontologies/compile
The binding is binding_for, the very one compile_ontology_actions takes at the save boundary, so this route cannot answer differently from the save it predicts. Every terminal is accepted, compile included: a terminal-less Definition (a Reaction's condition.set) reaches here as {...definition, "compile": {}}, and restricting the route to that one terminal would empty write_targets and skip the anchor, written-column and terminal-fitness checks that are the reason to ask (D1).
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 405
- 409
- 410
- 413
- 415
- 422
- 429
- 500
- 502
- 503
- 504
Successful Response
Bad Request
Unauthorized
Forbidden
Not Found
Method Not Allowed
Conflict
Gone
Request Entity Too Large
Unsupported Media Type
Unprocessable Entity
Too Many Requests
Internal Server Error
Bad Gateway
Service Unavailable
Gateway Timeout