# Downdetector

> Follow Downdetector Enterprise service status, incidents and consumer reports, compare baselines, and inspect report locations, cities, providers and networks.

App · 25 actions. Web page: https://docs.lodol.com/docs/integrations/downdetector

## Actions

### Get city

City details from Downdetector Enterprise.

**Inputs**

- Geo id (`geo_id`, number, required): Geo ID for Cities

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get company

Details from Downdetector Enterprise.

**Inputs**

- Company (`company_id`, number, required): Id for a company
- Fields (`fields`, list): Which fields to return in the output. The lesser you return, the faster the output can be. Only request the fields that you actually need in your views. **Status** The `status` field is a cached field for ease of use. It is advised to call the status endpoint `/company/[id]/status` for the latest status of a company. **Logos** The `logos` field is a special field, as it will return a dictionary of logo fields. If you only need the logo filename, you can use `logo`. **Contact** The `contact` field is a special field, as it will return a dictionary of contact fields. **ASNs*** If ASNs are configured for the company the `asns` field will return a list of ASN numbers. **Indicators** There are multi-level indicators possible, these will be presented as a "path-like" string, eg: - /animals/platypus - /animals/bird - etc. It is advised to display these as grouped under their respective paths, eg: ``` - Animals - Platypus - Bird ```. One or more of: `id`, `name`, `slug`, `url`, `stats_24` (Stats 24), `stats_60` (Stats 60), `baseline`, `baseline_current` (Baseline current), `category_id` (Category id), `logo`, and 19 more.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get company baseline

24h Baseline from Downdetector Enterprise.

**Inputs**

- Company (`company_id`, number, required): Id for a company

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get company recent reports

Number of reports in last 15 minutes from Downdetector Enterprise.

**Inputs**

- Company (`company_id`, number, required): Id for a company
- Sw (`sw`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Ne (`ne`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get company status

Current status from Downdetector Enterprise.

**Inputs**

- Company (`company_id`, number, required): Id for a company
- Ne (`ne`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Sw (`sw`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Threshold (`threshold`, number): Checks if status is above this threshold. If so, returns 'danger', if not, returns 'success'
- Indicator (`indicator`, text): Checks what the current status is for this indicator, only works with indicator_pct
- Indicator pct (`indicator_pct`, number): Checks if the given indicator is above this threshold. This is only true when the company breached the given threshold, or calculated baseline.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get country

Country details from Downdetector Enterprise.

**Inputs**

- Country iso (`country_iso`, text, required): ISO 2 string

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get current company baseline

Current Baseline from Downdetector Enterprise.

**Inputs**

- Company (`company_id`, number, required): Id for a company

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get current service heatmap

Heatmap for reports from Downdetector Enterprise.

**Inputs**

- Slugs (`slugs`, list, required): Slug to filter on
- Zoom (`zoom`, number): Zoom level for grouping. From 1 to 6.
- Countries (`countries`, list, required): Country ids to filter on
- Companies (`companies`, list): Company ids to filter on. You can get a list of relevant company ids from the `/slugs/<slug>/companies` endpoint.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get current service indicators

Current indicators for slugs from Downdetector Enterprise.

**Inputs**

- Slugs (`slugs`, list, required): Slug to filter on
- Countries (`countries`, list): Country ids to filter on
- Companies (`companies`, list): Company ids to filter on. You can get a list of relevant company ids from the `/slugs/<slug>/companies` endpoint.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get indicator

Indicator details from Downdetector Enterprise.

**Inputs**

- Indicator id (`indicator_id`, number, required): Indicator id

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get provider

Details from Downdetector Enterprise.

**Inputs**

- Network provider id (`network_provider_id`, number, required): Id for a provider

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get service cities

Cities for slugs from Downdetector Enterprise.

**Inputs**

- Slugs (`slugs`, list, required): Slug to filter on
- Location source (`location_source`, text): Filter on specific location source types. One of: `ip`, `device`.
- Startdate (`startdate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with enddate. - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Enddate (`enddate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with startdate. Enddate is inclusive. So selecting `2020-04-01T13:37:00+00:00` as enddate, will include all reports for that specific second as well. This could mean that the last bucket of a timeselection is always empty when it collides with a time bucket, eg, every 15 minutes. For example, given this period: `12:00:00 - 12:15:00`, will return 2 buckets: - 12:00:00 - 12:14:59 - 12:15:00 - 12:29:59 The contents of the buckets will be filtered on the given period, so the last bucket will only have the reports for the one second of the given period, which could give unexpected results. Instead, when using: `12:00:00 - 12:14:59`, only 1 bucket will be returned: - 12:00:00 - 12:14:59 - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Sw (`sw`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Ne (`ne`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Asn (`asn`, list): Filter reports on these network ids (ASN, RFC 1771)
- Amount (`amount`, number): Top X of buckets to return. From 10 to 512.
- Companies (`companies`, list): Company ids to filter on. You can get a list of relevant company ids from the `/slugs/<slug>/companies` endpoint.
- Countries (`countries`, list): Country ids to filter on
- Cities (`cities`, list): [BETA] City ids to filter on
- Providers (`providers`, list): [BETA] Provider ids to filter on
- Indicators (`indicators`, list): [BETA] Indicator ids to filter on

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get service countries

Countries for slugs from Downdetector Enterprise.

**Inputs**

- Slugs (`slugs`, list, required): Slug to filter on
- Startdate (`startdate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with enddate. - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Enddate (`enddate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with startdate. Enddate is inclusive. So selecting `2020-04-01T13:37:00+00:00` as enddate, will include all reports for that specific second as well. This could mean that the last bucket of a timeselection is always empty when it collides with a time bucket, eg, every 15 minutes. For example, given this period: `12:00:00 - 12:15:00`, will return 2 buckets: - 12:00:00 - 12:14:59 - 12:15:00 - 12:29:59 The contents of the buckets will be filtered on the given period, so the last bucket will only have the reports for the one second of the given period, which could give unexpected results. Instead, when using: `12:00:00 - 12:14:59`, only 1 bucket will be returned: - 12:00:00 - 12:14:59 - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Sw (`sw`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Ne (`ne`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Asn (`asn`, list): Filter reports on these network ids (ASN, RFC 1771)
- Amount (`amount`, number): Top X of buckets to return. From 10 to 512.
- Companies (`companies`, list): Company ids to filter on. You can get a list of relevant company ids from the `/slugs/<slug>/companies` endpoint.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get service indicators

Indicators for slugs from Downdetector Enterprise.

**Inputs**

- Slugs (`slugs`, list, required): Slug to filter on
- Location source (`location_source`, text): Filter on specific location source types. One of: `ip`, `device`.
- Startdate (`startdate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with enddate. - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Enddate (`enddate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with startdate. Enddate is inclusive. So selecting `2020-04-01T13:37:00+00:00` as enddate, will include all reports for that specific second as well. This could mean that the last bucket of a timeselection is always empty when it collides with a time bucket, eg, every 15 minutes. For example, given this period: `12:00:00 - 12:15:00`, will return 2 buckets: - 12:00:00 - 12:14:59 - 12:15:00 - 12:29:59 The contents of the buckets will be filtered on the given period, so the last bucket will only have the reports for the one second of the given period, which could give unexpected results. Instead, when using: `12:00:00 - 12:14:59`, only 1 bucket will be returned: - 12:00:00 - 12:14:59 - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Sw (`sw`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Ne (`ne`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Asn (`asn`, list): Filter reports on these network ids (ASN, RFC 1771)
- Amount (`amount`, number): Top X of buckets to return. From 10 to 512.
- Countries (`countries`, list): Country ids to filter on
- Companies (`companies`, list): Company ids to filter on. You can get a list of relevant company ids from the `/slugs/<slug>/companies` endpoint.
- Cities (`cities`, list): [BETA] City ids to filter on
- Providers (`providers`, list): [BETA] Provider ids to filter on
- Indicators (`indicators`, list): [BETA] Indicator ids to filter on

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get service networks

Networks for slugs from Downdetector Enterprise.

**Inputs**

- Slugs (`slugs`, list, required): Slug to filter on
- Startdate (`startdate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with enddate. - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Enddate (`enddate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with startdate. Enddate is inclusive. So selecting `2020-04-01T13:37:00+00:00` as enddate, will include all reports for that specific second as well. This could mean that the last bucket of a timeselection is always empty when it collides with a time bucket, eg, every 15 minutes. For example, given this period: `12:00:00 - 12:15:00`, will return 2 buckets: - 12:00:00 - 12:14:59 - 12:15:00 - 12:29:59 The contents of the buckets will be filtered on the given period, so the last bucket will only have the reports for the one second of the given period, which could give unexpected results. Instead, when using: `12:00:00 - 12:14:59`, only 1 bucket will be returned: - 12:00:00 - 12:14:59 - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Sw (`sw`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Ne (`ne`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Amount (`amount`, number): Top X of buckets to return. From 10 to 512.
- Countries (`countries`, list): Country ids to filter on
- Companies (`companies`, list): Company ids to filter on. You can get a list of relevant company ids from the `/slugs/<slug>/companies` endpoint.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get service providers

Providers for slugs from Downdetector Enterprise.

**Inputs**

- Slugs (`slugs`, list, required): Slug to filter on
- Location source (`location_source`, text): Filter on specific location source types. One of: `ip`, `device`.
- Startdate (`startdate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with enddate. - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Enddate (`enddate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with startdate. Enddate is inclusive. So selecting `2020-04-01T13:37:00+00:00` as enddate, will include all reports for that specific second as well. This could mean that the last bucket of a timeselection is always empty when it collides with a time bucket, eg, every 15 minutes. For example, given this period: `12:00:00 - 12:15:00`, will return 2 buckets: - 12:00:00 - 12:14:59 - 12:15:00 - 12:29:59 The contents of the buckets will be filtered on the given period, so the last bucket will only have the reports for the one second of the given period, which could give unexpected results. Instead, when using: `12:00:00 - 12:14:59`, only 1 bucket will be returned: - 12:00:00 - 12:14:59 - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Sw (`sw`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Ne (`ne`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Asn (`asn`, list): Filter reports on these network ids (ASN, RFC 1771)
- Amount (`amount`, number): Top X of buckets to return. From 10 to 512.
- Countries (`countries`, list): Country ids to filter on
- Companies (`companies`, list): Company ids to filter on. You can get a list of relevant company ids from the `/slugs/<slug>/companies` endpoint.
- Cities (`cities`, list): [BETA] City ids to filter on
- Providers (`providers`, list): [BETA] Provider ids to filter on
- Indicators (`indicators`, list): [BETA] Indicator ids to filter on

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get service reports

Reports for slugs from Downdetector Enterprise.

**Inputs**

- Slugs (`slugs`, list, required): Slug to filter on
- Location source (`location_source`, text): Filter on specific location source types. One of: `ip`, `device`.
- Startdate (`startdate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with enddate. - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Enddate (`enddate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with startdate. Enddate is inclusive. So selecting `2020-04-01T13:37:00+00:00` as enddate, will include all reports for that specific second as well. This could mean that the last bucket of a timeselection is always empty when it collides with a time bucket, eg, every 15 minutes. For example, given this period: `12:00:00 - 12:15:00`, will return 2 buckets: - 12:00:00 - 12:14:59 - 12:15:00 - 12:29:59 The contents of the buckets will be filtered on the given period, so the last bucket will only have the reports for the one second of the given period, which could give unexpected results. Instead, when using: `12:00:00 - 12:14:59`, only 1 bucket will be returned: - 12:00:00 - 12:14:59 - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Sw (`sw`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Ne (`ne`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Asn (`asn`, list): Filter reports on these network ids (ASN, RFC 1771)
- Providers (`providers`, list): [BETA] Provider ids to filter on
- Indicators (`indicators`, list): [BETA] Indicator ids to filter on
- Cities (`cities`, list): [BETA] City ids to filter on
- Interval (`interval`, text): Interval for the time based buckets, examples: 15m (15 minutes), 1m, 5m, 10m, 1h, 24h, 1d, 2d, etc.
- Offset (`offset`, text): Sets the offset for the bucket calculation. eg, if interval is set to 15 minutes, default buckets will be at :00, :15, :30, :45 marks. With this you can set the offset. For example given an interval of 15 minutes, and an offset of 7 minutes: :07, :22, :37, :52
- Companies (`companies`, list): Company ids to filter on. You can get a list of relevant company ids from the `/slugs/<slug>/companies` endpoint.
- Countries (`countries`, list): Country ids to filter on

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### Get site

Details from Downdetector Enterprise.

**Inputs**

- Site (`site_id`, number, required): Id for a site

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```

### List company events

Events from Downdetector Enterprise.

**Inputs**

- Company (`company_id`, number, required): Id for a company
- Startdate (`startdate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with enddate. - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Enddate (`enddate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with startdate. Enddate is inclusive. So selecting `2020-04-01T13:37:00+00:00` as enddate, will include all reports for that specific second as well. This could mean that the last bucket of a timeselection is always empty when it collides with a time bucket, eg, every 15 minutes. For example, given this period: `12:00:00 - 12:15:00`, will return 2 buckets: - 12:00:00 - 12:14:59 - 12:15:00 - 12:29:59 The contents of the buckets will be filtered on the given period, so the last bucket will only have the reports for the one second of the given period, which could give unexpected results. Instead, when using: `12:00:00 - 12:14:59`, only 1 bucket will be returned: - 12:00:00 - 12:14:59 - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Page size (`page_size`, number): Amount of results per page, between 10 and 100, defaults to 10. From 10 to 100.
- Page (`page`, text): On each query, a `X-Page-Next` header will be returned with a token as value. If the header has an empty value or is not present in the response headers, no other pages are available. For paging, provide this token for following pages. When calling the next pages, be sure to also include any initial parameters. Don't change those parameters while you are paging a resultset (they are part of the way the pageset is calculated).

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": []
  }
}
```

### List company incidents

Incidents from Downdetector Enterprise.

**Inputs**

- Company (`company_id`, number, required): Id for a company
- Peak attribution (`peak_attribution`, number): See the attribution endpoint for more information about attribution enums. One of: `0`, `1`, `2`, `3`.
- Peak user impact (`peak_user_impact`, number): See the attribution endpoint for more information about user impact enums. One of: `0`, `1`, `2`, `3`.
- Only active (`only_active`, true/false): When true, only the active incident will be returned
- Startdate (`startdate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with enddate. - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Enddate (`enddate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with startdate. Enddate is inclusive. So selecting `2020-04-01T13:37:00+00:00` as enddate, will include all reports for that specific second as well. This could mean that the last bucket of a timeselection is always empty when it collides with a time bucket, eg, every 15 minutes. For example, given this period: `12:00:00 - 12:15:00`, will return 2 buckets: - 12:00:00 - 12:14:59 - 12:15:00 - 12:29:59 The contents of the buckets will be filtered on the given period, so the last bucket will only have the reports for the one second of the given period, which could give unexpected results. Instead, when using: `12:00:00 - 12:14:59`, only 1 bucket will be returned: - 12:00:00 - 12:14:59 - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Page (`page`, number): Requested page number. At least 1.
- Page size (`page_size`, number): Amount of results per page, between 10 and 100, defaults to 10. From 10 to 100.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": []
  }
}
```

### List incidents

Incidents from Downdetector Enterprise.

**Inputs**

- Startdate (`startdate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with enddate. - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Enddate (`enddate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with startdate. Enddate is inclusive. So selecting `2020-04-01T13:37:00+00:00` as enddate, will include all reports for that specific second as well. This could mean that the last bucket of a timeselection is always empty when it collides with a time bucket, eg, every 15 minutes. For example, given this period: `12:00:00 - 12:15:00`, will return 2 buckets: - 12:00:00 - 12:14:59 - 12:15:00 - 12:29:59 The contents of the buckets will be filtered on the given period, so the last bucket will only have the reports for the one second of the given period, which could give unexpected results. Instead, when using: `12:00:00 - 12:14:59`, only 1 bucket will be returned: - 12:00:00 - 12:14:59 - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Only active (`only_active`, true/false): When true, only the active incident will be returned
- Peak attribution (`peak_attribution`, number): See the attribution endpoint for more information about attribution enums. One of: `0`, `1`, `2`, `3`.
- Peak user impact (`peak_user_impact`, number): See the attribution endpoint for more information about user impact enums. One of: `0`, `1`, `2`, `3`.
- Page (`page`, number): Requested page number. At least 1.
- Page size (`page_size`, number): Amount of results per page, between 10 and 100, defaults to 10. From 10 to 100.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": []
  }
}
```

### List report locations

Locations for reports from Downdetector Enterprise.

**Inputs**

- Slugs (`slugs`, list, required): Slug to filter on
- Page (`page`, text): On each query, a `X-Page-Next` header will be returned with a token as value. If the header has an empty value or is not present in the response headers, no other pages are available. For paging, provide this token for following pages. When calling the next pages, be sure to also include any initial parameters. Don't change those parameters while you are paging a resultset (they are part of the way the pageset is calculated).
- Page size (`page_size`, number): Amount of results per page. From 10 to 1000.
- Location source (`location_source`, text): Filter on specific location source types. One of: `ip`, `device`.
- Startdate (`startdate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with enddate. - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Enddate (`enddate`, date and time): ISO8601, limits the results to start on this date, only works in conjunction with startdate. Enddate is inclusive. So selecting `2020-04-01T13:37:00+00:00` as enddate, will include all reports for that specific second as well. This could mean that the last bucket of a timeselection is always empty when it collides with a time bucket, eg, every 15 minutes. For example, given this period: `12:00:00 - 12:15:00`, will return 2 buckets: - 12:00:00 - 12:14:59 - 12:15:00 - 12:29:59 The contents of the buckets will be filtered on the given period, so the last bucket will only have the reports for the one second of the given period, which could give unexpected results. Instead, when using: `12:00:00 - 12:14:59`, only 1 bucket will be returned: - 12:00:00 - 12:14:59 - Be aware that the `+` in RFC3339 format needs to be urlencoded. - Be aware that the timezone is divided by a colon in ISO8601, eg: `2042-03-14T13:37:42+01:00`
- Sw (`sw`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Ne (`ne`, list): Bounds for the query. Latitude,longitude pair, comma seperated, eg: `5.4123,21.0012`
- Asn (`asn`, list): Filter reports on these network ids (ASN, RFC 1771)
- Companies (`companies`, list): Company ids to filter on. You can get a list of relevant company ids from the `/slugs/<slug>/companies` endpoint.
- Countries (`countries`, list): Country ids to filter on
- Cities (`cities`, list): [BETA] City ids to filter on
- Providers (`providers`, list): [BETA] Provider ids to filter on
- Indicators (`indicators`, list): [BETA] Indicator ids to filter on
- Max pages (`max_pages`, number): Maximum pages to fetch immediately, 1 to 100; default 5. Check pagination.complete before treating the results as complete. From 1 to 100.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": []
  }
}
```

### List service companies

Companies for slugs from Downdetector Enterprise.

**Inputs**

- Slugs (`slugs`, list, required): Slug to filter on
- Fields (`fields`, list): Which fields to return in the output. The lesser you return, the faster the output can be. Only request the fields that you actually need in your views. **Status** The `status` field is a cached field for ease of use. It is advised to call the status endpoint `/company/[id]/status` for the latest status of a company. **Logos** The `logos` field is a special field, as it will return a dictionary of logo fields. If you only need the logo filename, you can use `logo`. **Contact** The `contact` field is a special field, as it will return a dictionary of contact fields. **ASNs*** If ASNs are configured for the company the `asns` field will return a list of ASN numbers. **Indicators** There are multi-level indicators possible, these will be presented as a "path-like" string, eg: - /animals/platypus - /animals/bird - etc. It is advised to display these as grouped under their respective paths, eg: ``` - Animals - Platypus - Bird ```. One or more of: `id`, `name`, `slug`, `url`, `stats_24` (Stats 24), `stats_60` (Stats 60), `baseline`, `baseline_current` (Baseline current), `category_id` (Category id), `logo`, and 19 more.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": []
  }
}
```

### List sites

List of available sites from Downdetector Enterprise.

**Inputs**: None.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": []
  }
}
```

### Search companies

Search companies from Downdetector Enterprise.

**Inputs**

- Fields (`fields`, list): Which fields to return in the output. The lesser you return, the faster the output can be. Only request the fields that you actually need in your views. Note: `/companies/search` restricts to a narrow allowlist (`id`, `name`, `slug`, `url`, `country_iso`, `country_id`, `category_id`) once DD-9725 is live. For real-time status, statistics, indicators, and other rich fields, use `/companies/{company_id}`. One or more of: `id`, `name`, `slug`, `url`, `stats_24` (Stats 24), `stats_60` (Stats 60), `baseline`, `baseline_current` (Baseline current), `category_id` (Category id), `logo`, and 18 more.
- Name (`name`, text): Company name to filter for, this will be a partial match, case insensitive.
- Country (`country`, text): Country to filter on, iso 2
- Category id (`category_id`, number): Category id to filter on
- Slug (`slug`, text): Slug to filter on, full match
- Page (`page`, number): 1-indexed page number for paginated results. At least 1.
- Page size (`page_size`, number): Number of results per page, between 10 and 100. From 10 to 100.

**Outputs**

- `response` (object): The complete service response, including resource data and pagination fields.

**Example output**

```json
{
  "response": {
    "data": {
      "id": "qa-resource"
    }
  }
}
```
