Page Comparison

Table of Contents

Note: This is Reference for v2 of Logsene API.

...

Introduction to Management API

...

Access to API key of some Account is allowed for OWNER, BILLING_ADMIN and ADMIN users. Users with USER role cannot access API key of that Account, though they can always use their own Account's API key to manage their own Account, Apps, etc. For more info about Account Sharing please see SPM FAQ.

Elasticsearch-compatible Search API

To use the search APIs, see Search through the Elasticsearch API. This API is fully compatible with Elasticsearch's APIs. To use it you need just your Logsene App tokens, not the API key. The rest of this document describes only the app management APIs. For searching your logs from the terminal/console, see Logsene CLI.

Request/Response format

All API calls accept JSON in requests and return JSON response. All API call requests should contain apiKey attribute (among other attributes specific for that API call). Example of content of one such call:

Code Block
{ "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5", "name":"new-logsene-app-1" }

All API responses contain attribute success which has value true or false. Optional response attributes are message (which provides textual message about what API call did) and data (which contains data returned by the call). Example of response:

Code Block

{
  "success" : true,
  "message" : "Created application for dto: [name=new-logsene-app-1,apiKey=a9092d95-d062-4499-ad0b-a1b43fadb9b5], token is: 61611d45-6ecd-47f7-b5b4-6faccdb2f8c4",
  "data" : {
    "token" : {
      "new-logsene-app-1" : "61611d45-6ecd-47f7-b5b4-6faccdb2f8c4"
    }
  }
}

Also, all responses contain an HTTP code which describes success or failure. In case of a successful call, HTTP code will be 200 (OK). Any other non-2XX HTTP code represents an error (most commonly used codes are 400 - Bad Request, 401 - Unauthorized, 403 - Forbidden and 500 - Internal Server Error).

Apps API

Create Logsene App

Creates new Logsene app under referenced account.

API call

HTTP Method

Attributes

Description

https://apps.sematext.com/logsene-reports/api/v2/app/add

POST

apiKey (of account under which app will be created)

name (of app which will be created)

discountCode (optional parameter, send only if you have a valid code)

Creates new Logsene application under account defined by apiKey, with name name (such name should be unique among other Logsene apps under this account)

Example of API call:

Code Block
curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/app/add" -d ' { "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5", "name":"new-logsene-app-1" }'

Example of success response (with HTTP status 200):

Code Block

{
  "success" : true,
  "message" : "Created application for dto: [name=new-logsene-app-1,apiKey=a9092d95-d062-4499-ad0b-a1b43fadb9b5], token is: 61611d45-6ecd-47f7-b5b4-6faccdb2f8c4",
  "data" : {
    "token" : {
      "new-logsene-app-1" : "61611d45-6ecd-47f7-b5b4-6faccdb2f8c4"
    }
  }
}

Example of non-200 response:

Code Block
{ "success" : false, "message" : "User identified with API key a9092d95-d062-4499-ad0b-a1b43fadb9b4 doesn't exist" }

List Apps

API call	HTTP Method	Attributes	Description
https://apps.sematext.com/users-web/api/v2/app/list	POST	apiKey (of account whose apps are fetched)	Fetches all apps which can be accessed by account represented with apiKey. All app roles will be included (OWNER, ADMIN, USER). Apps available through sharing of other accounts will not be returned.

Example of API call:

Code Block
curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/users-web/api/v2/app/list" -d ' { "apiKey":"a9092d95-d06-4499-ad0b-a1b43fadb9b5" }'

Example of a success response (with HTTP code 200):

Code Block

{
  "success" : true,
  "data" : {
    "apps" : {
      "logsene" : [ {
        "planId" : "10000",
        "trialEndDate" : "Sun Jul 17 23:59:59 UTC 2015",
        "appType" : "Logsene",
        "appStatus" : "ACTIVE",
        "ownerEmail" : "some-email-address@your-company.com",
        "planName" : "Basic Logsene",
        "token" : "01f1d605-8ab4-4a08-bf7e-ef2749e90de5",
        "service" : "logsene",
        "role" : "USER",
        "name" : "logsene1"
      }, {
        "planId" : "10000",
        "trialEndDate" : "Sun Jul 17 23:59:59 UTC 2015",
        "appType" : "Logsene",
        "appStatus" : "ACTIVE",
        "ownerEmail" : "some-email-address@your-company.com",
        "planName" : "Basic Logsene",
        "token" : "61ae423c-9e81-4201-9a57-30442196200d",
        "service" : "logsene",
        "role" : "ADMIN",
        "name" : "logsene2"
      }, {
.
.
.
      }, {
        "planId" : "27",
        "trialEndDate" : "Sun Feb 17 23:59:59 UTC 2015",
        "appType" : "Solr",
        "appStatus" : "ACTIVE",
        "ownerEmail" : "some-email-address@your-company.com",
        "planName" : "Pro Silver SPM Solr",
        "token" : "61611d45-6ecd-47f7-b5b4-6faccdb2f8c4",
        "service" : "spm",
        "role" : "OWNER",
        "name" : "spmSolr1"
      } ]
    }
  }
}

Note: It will return all apps registered under provided account, not just Logsene apps.

Alerts API

Logsene Alerts HTTP API lets you:

list all alerts defined for some app
delete/enable/disable individual alerts
create new alerts (of any type: threshold, anomaly)
list alert notifications

When using Logsene Alerts API, you will need to use API key which belongs to OWNER of the app to which alerts are related. If you are managing alerts for your apps, then just use your API key. If you are managing alerts for apps that belong to some other account (and your are just a guest in that account with role BILLING_ADMIN or ADMIN), you will have to use API key of that account (in both cases the key can be found here, you just have to consider which account you are currently logged into).

List Alerts

Fetches all alerts of specific type (threshold, anomaly) for a particular Logsene app.

API call

HTTP Method

Attributes

Description

https://apps.sematext.com/logsene-reports/api/v2/alert/threshold/list

POST

apiKey (of owner of app represented with "token")

appToken (of app whose alerts are fetched)

Fetches all threshold based alerts for app defined with appToken

https://apps.sematext.com/logsene-reports/api/v2/alert/anomaly/list

POST

apiKey (of owner of app represented with "token")

appToken (of app whose alerts are fetched)

Fetches all anomaly alerts for app defined with appToken

Examples of API calls:

Code Block

curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/threshold/list" -d '
{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"12c91563-ba95-4a73-aa5a-08fe04b94631"
}'
 
curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/anomaly/list" -d '
{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"12c91563-ba95-4a73-aa5a-08fe04b94631"
}'

Example of success response (with HTTP status 200):

Code Block

{

  "success" : true,
  "data" : {
    "alertRules" : {
      "140" : {
        "sendToEmail" : "email-to-send-alerts-to@your-company.com",
        "muteTimePeriodInMinutes" : "30",
        "minDelayBetweenNotificationsInMinutes" : "60",
        "maxNotificationsInMutePeriod" : 3,
        "ignoreRegularEventsEnabled" : false,
        "muteIsGlobal" : false,
        "analyzingTime" : "300",
        "enabled" : true,
        "name" : "Apache Alert",
        "query" : "apache",
        "estimateOperation" : "LESS_OR_EQUAL",
        "estimateValue" : 0.0,
        "backToNormalNeeded" : false
      },
      "149" : {
        "sendToEmail" : "email-to-send-alerts-to@your-company.com",
        "muteTimePeriodInMinutes" : "30",
        "minDelayBetweenNotificationsInMinutes" : "60",
        "maxNotificationsInMutePeriod" : 3,
        "ignoreRegularEventsEnabled" : false,
        "muteIsGlobal" : false,
        "analyzingTime" : "300",
        "enabled" : true,
        "name" : "Warn Alert",
        "query" : "warn",
        "estimateOperation" : "MORE",
        "estimateValue" : 500.0,
        "backToNormalNeeded" : false
      }
    }
  }
}

If response succeeded, HTTP code will be 200 and response content will be a map where keys are alert IDs (which can be used as parameter in other Alerts API calls) and values are alert objects. The previous example shows "threshold" alerts; other alert types will show different attributes in alert objects.

The output of this call can be directly reused for creation of new alerts, you can just copy alert objects and reuse them (or you can also adjust some attributes).

Create Alert

There are 2 types of alerts available in Logsene - threshold and anomaly. Each of them has different attributes so there are 2 different API calls for creating them.

Threshold and Anomaly Alerts are created for a specific query.

Create Threshold Alert

API call

HTTP Method

Attributes

Description

https://apps.sematext.com/logsene-reports/api/v2/alert/threshold/add

POST

apiKey (of owner of app represented with "token")

appToken (of app for which alert is created)

+ attributes specific to threshold alert

Creates new threshold based query alert for Logsene app defined with appToken

Example of API call:

Code Block

curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/threshold/add" -d '
{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"12c91563-ba95-4a73-aa5a-08fe04b94631",
  "alertRule":{
    "name":"Apache alert",
    "query":"apache",
    "enabled":true,
    "estimateValue":500,
    "estimateOperation":"MORE",
    "analyzingTime":5,
    "backToNormalNeeded":false,
    "ignoreRegularEventsEnabled":false,
    "muteTimePeriodInMinutes":30,
    "minDelayBetweenNotificationsInMinutes":1,
    "maxNotificationsInMutePeriod":3,
    "muteIsGlobal":false,
    "sendToEmail":"email-to-send-alerts-to@your-company.com",
    "ruleType": "AFValuesRule"
   }
}'

Example of a success response (with HTTP code 200):

Code Block

{
  "success" : true,
  "message" : "Alert rule created",
  "data" : {
    "alertRule" : {
      "sendToEmail" : "email-to-send-alerts-to@your-company.com",
      "muteTimePeriodInMinutes" : "30",
      "minDelayBetweenNotificationsInMinutes" : "1",
      "maxNotificationsInMutePeriod" : 3,
      "ignoreRegularEventsEnabled" : false,
      "muteIsGlobal" : false,
      "analyzingTime" : "05",
      "systemId" : 2199,
      "enabled" : true,
      "name" : "Apache Alert",
      "query" : "apache",
      "estimateOperation" : "MORE",
      "estimateValue" : 500.0,
      "backToNormalNeeded" : false
    }
  }
}

Create Anomaly Alert

...

API call

...

HTTP Method

...

Attributes

...

Description

...

apiKey (of owner of app represented with "token")

appToken (of app for which alert is created)

+ attributes specific to anomaly alert

...

Example of API call:

Code Block

curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/anomaly/add" -d '
{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"12c91563-ba95-4a73-aa5a-08fe04b94631",
  "alertRule":{
    "name":"Anomaly apache alert",
    "query":"apache",
    "enabled":"true",
    "backToNormalNeeded":false,
    "ignoreRegularEventsEnabled":true,
    "muteTimePeriodInMinutes":"30",
    "analyzingTime" : "05",
    "minDelayBetweenNotificationsInMinutes":"1",
    "maxNotificationsInMutePeriod":"3",
    "muteIsGlobal":false,
    "sendToEmail":"email-to-send-alerts-to@your-company.com",
    "ruleType": "AFAnomalyValuesRule"
   }
}'

Example of a success response (with HTTP code 200):

Code Block

{
  "success" : true,
  "message" : "Alert rule created",
  "data" : {
    "alertRule" : {
      "sendToEmail" : "email-to-send-alerts-to@your-company.com",
      "muteTimePeriodInMinutes" : "30",
      "minDelayBetweenNotificationsInMinutes" : "1",
      "maxNotificationsInMutePeriod" : 3,
      "ignoreRegularEventsEnabled" : true,
      "muteIsGlobal" : false,
      "analyzingTime" : "60",
      "systemId" : 2199,
      "enabled" : true,
      "name" : "Anomaly apache alert",
      "query" : "apache",
      "backToNormalNeeded" : false
    }
  }
}

Errors will be returned in case of wrong apiKey or appToken or if some of values are missing. Example of a error response when query is not sent (with HTTP code 400):

Code Block
{ "success" : false, "message" : "Missing mandatory param alertRule.query" }

Delete Alert

API call

HTTP Method

Attributes

Description

https://apps.sematext.com/logsene-reports/api/v2/alert/delete/{alertId}

DELETE

apiKey (of owner of app represented with "token")

appToken (of app to which alert belongs)

Deletes a single alert rule

Note: {alertId} value in URL should be replaced with real id of alert rule which should be deleted - alertId of each alert is returned as a key in list alerts API call response.

Example API call:

Code Block

curl -X DELETE -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/delete/141" -d '{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"12c91563-ba95-4a73-aa5a-08fe04b94631"
}'

Example of a success response (with HTTP code 200):

Code Block
{ "success" : true, "message" : "Alert with alertId 141 deleted", "data" : { "alertId" : "141" } }

Enable/Disable Alert

API call	HTTP Method	Attributes	Description
https://apps.sematext.com/logsene-reports/api/v2/alert/enable/{alertId}	POST	apiKey (of owner of app whose alert is enabled) appToken (of app to which alert belongs)	Enables alert
https://apps.sematext.com/logsene-reports/api/v2/alert/disable/{alertId}	POST	apiKey (of owner of app whose alert is enabled) appToken (of app to which alert belongs)	Disables alert

Note: {alertId} value in URL should be replaced with real id of alert rule which should be deleted - alertId of each alert is returned as a key in list alerts API call response.

Example API calls:

Code Block

curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/enable/141" -d '{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"12c91563-ba95-4a73-aa5a-08fe04b94631"
}'

curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/disable/141" -d '{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"12c91563-ba95-4a73-aa5a-08fe04b94631"
}'

Example of a success responses (with HTTP code 200):

Code Block
{ "success" : true, "message" : "Alert with alertId 141 enabled", "data" : { "alertId" : "141" } } { "success" : true, "message" : "Alert with alertId 141 disabled", "data" : { "alertId" : "141" } }

List Alert Notifications (Coming soon!)

API call

HTTP Method

Attributes

Description

https://apps.sematext.com/logsene-reports/api/v2/alert/notification/list

POST

apiKey (of owner of apps whose alert notifications want to list)

appToken (of app to list alert notifications for; it is optional - if omitted, alerts for all active apps will be returned)

start (time of interval to return alert notifications for; optional; can be expressed as timestamp in milliseconds or UTC date in format yyyy-MM-dd HH:mm:ss)

end (time of interval to return alert notifications for; optional; can be expressed as timestamp in milliseconds or UTC date in format yyyy-MM-dd HH:mm:ss)

interval (to return alert notifications for,expressed in milliseconds; optional; Can use suffixes s, m, h, d to express interval in seconds, minutes, hours, days - e.g. "1d" is equal to "86400000" )

List alerts for provided user, app and defined time interval.

Examples of API calls:

Code Block

# alert notifications for last 24h for all apps owned by user with provided key
curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/notification/list" -d '{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5"
}'
 
# alert notifications for last 24h for app with provided token
curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/notification/list" -d '{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"12c91563-ba95-4a73-aa5a-08fe04b94631"
}'
 
# alert notifications for one hour interval specified with start and end
curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/notification/list" -d '{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "start":"2015-07-28 12:36:14",
  "end":"2015-07-28 13:36:14",
}'
 
# alert notifications for last hour
curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/notification/list" -d '{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "interval":"1h",
}'
 
# alert notifications created after timestamp provided in start
curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/alert/notification/list" -d '{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "start":"1438086975139"
}'

Example of success response (with HTTP code 200):

Code Block

{
  "success" : true,
  "data" : {
    "alerts" : [ {
      "when" : "23 hours ago",
      "text" : "Test alert",
      "createTime" : "2015-07-28 13:38:26",
      "backToNormal" : false,
      "appName" : "logsene-api-test",
      "appType" : "Logsene",
      "sent" : true
    }, {
      "when" : "23 hours ago",
      "text" : "Test alert",
      "createTime" : "2015-07-28 13:35:11",
      "backToNormal" : false,
      "appName" : "test-logsene",
      "appType" : "Logsene",
      "sent" : true
    } ],
    "start" : "2015-07-28 12:36:15",
    "end" : "2015-07-29 12:36:15"
  }
}

Regardless on how input is defined, output will contain list of alert notifications matching criteria and start and end dates of returned interval. Following tables explains rules how star, end and interval are combined.

"start"	"end"	"interval"	Rule
No	No	No	[current - 24h, current]
No	No	Yes	[current - interval, current]
No	Yes	No	[end - 24h, end]
No	Yes	Yes	[end - interval, end]
Yes	No	No	[start, current]
Yes	No	Yes	[start, start + interval]
Yes	Yes	No	[start, end]
Yes	Yes	Yes	[start, end]

Subscriptions API

Subscriptions API provides API calls for fetching of existing subscriptions and for triggering emailing of reports.

List Subscriptions

For particular Logsene application, this API call will return a list of all existing subscriptions.

...

API call

...

HTTP Method

...

Attributes

...

Description

https://apps.sematext.com/logsene-reports/api/v2/subscription/list

...

apiKey (of owner of app represented with "token")

appToken (token of app whose metrics info is being fetched)

...

Fetches subscriptions for Logsene app defined with appToken.

Example of API call:

Code Block

curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/subscription/list -d '
{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"01f1d605-8ab4-4a08-bf7e-ef2749e90de5"
}'

Example of a success response (with HTTP code 200):

Code Block

{
  "success" : true,
  "data" : {
    "subscriptions" : [ {
      "subscriptionId" : "55",
      "subject" : "[Sematext Logsene] 'Query: warning' for 'Logsene web server' application.",
      "appToken" : "01f1d605-8ab4-4a08-bf7e-ef2749e90de5",
      "appName" : "logsene1",
      "timeRange" : "ONE_WEEK",
      "attributes" : [ "report name = Query: warning, filters: " ],
      "emailTo" : [ "email-to-send-alerts-to@your-company.com" ]
    }, {      "subscriptionId" : "76",
      "subject" : "[Sematext Logsene] 'Query: error' for 'Logsene web server' application.",
      "appToken" : "01f1d605-8ab4-4a08-bf7e-ef2749e90de5",
      "appName" : "logsene1",
      "timeRange" : "ONE_WEEK",
      "attributes" : [ "report name = Query: error, filters: " ],
      "emailTo" : [ "email-to-send-alerts-to@your-company.com" ]
    } ]

  }
}

Email Report

Triggers instant emailing of a report defined by some subscription.

...

https://apps.sematext.com/logsene-reports/api/v2/subscription/send/{subscriptionId}

...

apiKey (of owner of app represented with "token")

appToken (token of app whose metrics info is being fetched)

...

Example of API call:

Code Block

curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/subscription/send/36" -d '
{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"262f66e5-0951-488b-9c92-379ba71a4299"
}'

Example of a success response (with HTTP code 200):

Code Block
{ "success" : true, "message" : "Report for subscription with ID 36 sent" }

Saved Queries API (Coming soon!)

Logsene Saved Queries HTTP API lets you:

list all saved queries defined for some app
delete individual saved queries
create new saved query

When using Logsene Saved Queries API, you will need to use API key which belongs to OWNER of the app to which saved queries are related. If you are managing saved queries for your apps, then just use your API key. If you are managing saved queries for apps that belong to some other account (and your are just a guest in that account with role BILLING_ADMIN or ADMIN), you will have to use API key of that account (in both cases the key can be found here, you just have to consider which account you are currently logged into).

List Saved Queries

Fetches saved queries for a particular Logsene app.

API call

HTTP Method

Attributes

Description

https://apps.sematext.com/logsene-reports/api/v2/query/list

POST

apiKey (of owner of app represented with "token")

appToken (of app whose saved queries are fetched)

Fetches all saved queries for app defined with appToken

Examples of API calls:

Code Block

curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/query/list" -d '
{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"12c91563-ba95-4a73-aa5a-08fe04b94631"
}'

Example of success response (with HTTP status 200):

Code Block
{ "success" : true, "data" : { "queries" : { "14" : { "queryName" : "Chrome query", "queryString" : "Chrome", }, "49" : { "queryName" : "Localhost", "queryString" : "host:(127.0.0.1)", } } } }

If response succeeded, HTTP code will be 200 and response content will be a map where keys are query IDs (which can be used as parameter in delete saved query API call) and values are query objects.

Create Saved Query

API call

HTTP Method

Attributes

Description

https://apps.sematext.com/logsene-reports/api/v2/query/add

POST

apiKey (of owner of app represented with "token")

appToken (of app for which saved query is created)

queryName (display name, does not have to be unique)

queryString (saved query string)

Creates new saved query with provided name and query string for Logsene app defined with appToken

Example of API call:

Code Block

curl -X POST -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/query/add" -d '
{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"12c91563-ba95-4a73-aa5a-08fe04b94631",
  "query":{
    "queryName" : "Hot",
    "queryString" : "tag:(hot)"
  }
}'

Example of a success response (with HTTP code 200):

Code Block
{ "success" : true, "message" : "Query created", "data" : { "query":{ "id" : 50, "queryName" : "Hot", "queryString" : "tag:(hot)" } } }

Delete Saved Query

...

apiKey (of owner of app represented with "token")

appToken (of app to which saved query belongs to)

...

Note: {queryId} value in URL should be replaced with real id of saved query which should be deleted - queryId of each saved query is returned as a key in list saved queries API call response.

Example API call:

Code Block

curl -X DELETE -k -H "Content-Type: application/json" "https://apps.sematext.com/logsene-reports/api/v2/query/delete/50" -d '{
  "apiKey":"a9092d95-d062-4499-ad0b-a1b43fadb9b5",
  "appToken":"12c91563-ba95-4a73-aa5a-08fe04b94631"
}'

Example of a success response (with HTTP code 200):

Code Block
{ "success" : true, "message" : "Query with queryId 50 deleted", "data" : { "queryId" : "50" } }

Elasticsearch-compatible API

...

Documentation moved to http://sematext.com/docs/logs/logsene-api-reference/

Versions Compared

Old Version 40

New Version Current

Key

Introduction to Management API

Elasticsearch-compatible Search API

Request/Response format

Apps API

Create Logsene App

List Apps

Alerts API

List Alerts

Create Alert

Create Threshold Alert

Create Anomaly Alert

Delete Alert

Enable/Disable Alert

List Alert Notifications (Coming soon!)

Subscriptions API

List Subscriptions

Email Report

Saved Queries API (Coming soon!)

List Saved Queries

Create Saved Query

Delete Saved Query

Elasticsearch-compatible API