From ead24d5350f3e51549b8eb76f43a51457f3d2b6f Mon Sep 17 00:00:00 2001 From: Alexander J Date: Mon, 28 May 2018 16:29:50 +0200 Subject: [PATCH 1/2] That is how an event JSON object should look like That is how an event JSON object should look like --- automation/README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/automation/README.md b/automation/README.md index a93d451..1cf3682 100644 --- a/automation/README.md +++ b/automation/README.md @@ -128,6 +128,15 @@ curl --header "Authorization: YOUR API KEY" --header "Accept: application/json" curl -i -H "Accept: application/json" -H "content-type: application/json" -H "Authorization: a4PLf8QICdDdOmFjwdtSYqkCqn9CvN0VQt7mpUUf" --data "@event.json" -X POST http://10.50.13.60/events ~~~~ +~~~~ +curl -i -H "Accept: application/json" -H "content-type: application/json" -H "Authorization: a4PLf8QICdDdOmFjwdtSYqkCqn9CvN0VQt7mpUUf" --data "@event.json" -X POST http://10.50.13.60/events +~~~~ + +That is how an event JSON object should look like +~~~~json +{"Event":{"date":"2015-01-01","threat_level_id":"1","info":"testevent","published":false,"analysis":"0","distribution":"0","Attribute":[{"type":"domain","category":"Network activity","to_ids":false,"distribution":"0","comment":"","value":"test.com"}]}} +~~~~ + ### DELETE /events #### Description From b6b13f3a28ef62f874ea382ac5cb7a21fd834a01 Mon Sep 17 00:00:00 2001 From: Alexander J Date: Mon, 28 May 2018 16:32:01 +0200 Subject: [PATCH 2/2] Update README.md --- automation/README.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/automation/README.md b/automation/README.md index 1cf3682..277b89d 100644 --- a/automation/README.md +++ b/automation/README.md @@ -128,10 +128,6 @@ curl --header "Authorization: YOUR API KEY" --header "Accept: application/json" curl -i -H "Accept: application/json" -H "content-type: application/json" -H "Authorization: a4PLf8QICdDdOmFjwdtSYqkCqn9CvN0VQt7mpUUf" --data "@event.json" -X POST http://10.50.13.60/events ~~~~ -~~~~ -curl -i -H "Accept: application/json" -H "content-type: application/json" -H "Authorization: a4PLf8QICdDdOmFjwdtSYqkCqn9CvN0VQt7mpUUf" --data "@event.json" -X POST http://10.50.13.60/events -~~~~ - That is how an event JSON object should look like ~~~~json {"Event":{"date":"2015-01-01","threat_level_id":"1","info":"testevent","published":false,"analysis":"0","distribution":"0","Attribute":[{"type":"domain","category":"Network activity","to_ids":false,"distribution":"0","comment":"","value":"test.com"}]}}