How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

watchTowr Cloud Storage API

The Cloud Storage API from watchTowr — 3 operation(s) for cloud storage.

watchTowr Cloud Storage API is one of 20 APIs that watchTowr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cloud Storage. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 3 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://{tenant}.{region}.watchtowr.io.

3 operations 3 paths 4 schemas 2 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{tenant}.{region}.watchtowr.io
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

watchTowr Cloud Storage API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — API key issued from the watchTowr Platform dashboard (Settings - API Management / Integrations - Client API), sent as a Bearer token.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 2 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Cloud Storage 3
GET
/api/client/assets/cloudStorage/list
List all cloud storage assets
get_list_asset_cloud_storages 2 params → 200401403
GET
/api/client/assets/cloudStorage/show/{id}
Show the details of a cloud storage asset
get_asset_cloud_storage_details 1 param → 200401403404
PUT
/api/client/assets/cloudStorage/update-status/{id}
Update the status of a cloud storage asset
update_asset_cloud_storage_status 1 param body → 200401403404422

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are UnprocessableContent (2 properties), Unauthorized (1 property), ForbiddenResponse (1 property), NotFound (1 property). Each schema is shown below with its type and property counts.

NotFound
object
1 property
UnprocessableContent
object
2 properties
ForbiddenResponse
object
1 property
Unauthorized
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

watchtowr-cloud-storage-api-openapi.yml Raw ↑

Other APIs watchTowr publishes across the network.

watchTowr Activity Log API
watchTowr Assets API
watchTowr Business Unit API
watchTowr Certificates API
watchTowr Containers API
watchTowr Domains API
watchTowr Findings API
watchTowr Hunts API
watchTowr IP Addresses API
watchTowr IP Ranges API
watchTowr Mobile Applications API
watchTowr Points of Interest API
Where this information came from

This is an independent, third-party profile of watchTowr Cloud Storage API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.