Skip to main content
POST
Upload Ontology

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

multipart/form-data
ontology_key
string
required

Unique, user-defined identifier for this ontology. Reference it later via the ontology_key parameter of the cognify/remember endpoints.

Example:

"medical_ontology"

ontology_file
file
required

Single ontology file in any RDF serialization rdflib parses. The format is taken from the filename extension (.owl, .rdf, .xml, .ttl, .n3, .jsonld, .nt, .nq, .trig), or - when the extension is not one of these - from the part's Content-Type (application/ld+json, application/n-quads, application/n-triples, application/rdf+xml, application/trig, application/x-turtle, application/xml, text/n3, text/turtle, text/xml). Files matching neither are rejected with 400. Exactly one file per request.

description
string | null

Optional human-readable description (plain string; values starting with '[' or '{' are rejected).

Example:

"OWL ontology of medical conditions and treatments"

Response

Successful Response

The response is of type Response Upload Ontology Api V1 Ontologies Post · object.