POST secondary-entity/delete
Delete a secondary entity in a graph of a secondary ontology.
Request Information
Headers
HTTP_AUTHORIZATION: Required. OAuth 1.0 parameters with the OAuth signature of the url you are going to request. The consumer keys and access token can be obtained from the community administration.
Sample:HTTP_AUTHORIZATION: OAuth oauth_token="CObXqjfOisVh9%2F2GjC7NNd8BCzY%3D", oauth_consumer_key="clGACsiGaMp%2FD%2BUwkSvRBxA1k50%3D", oauth_nonce="VqKza6d5x1HpPQWFe08spbdOnkTQpfaLfD9Oeuyg", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1462882011", oauth_signature="RH5aKKKJaEvK5cIsZZzXtFh7cCk%3D"
Body Parameters
Name | Description | Type | Additional information |
---|---|---|---|
ontology_url |
Ontology url |
string |
Required |
community_short_name |
Communtiy short name |
string |
Required |
entity_id |
The secondary entity identificator |
string |
Required |
Request Formats
application/json, text/json
Sample:
{ "ontology_url": "http://gnoss.com/Ontologia/Application.owl", "community_short_name": "developers", "entity_id": "http://gnoss.com/items/application_9ba0230b-0375-4242-83ee-f402ef68b503_c70d16e6-6132-4f6c-b975-1c63b8c446d2" }
Response Information
Response HTTP status code
On success, the response contains 200 code.
On fail, throws a WebException with code:
- 401 Unauthorized if the OAuth signature is invalid
- 400 Bad Request if the params are invalid
- 500 Internal server error if something goes wrong...