Sensors Data · OpenAPI Overlay 1.0.0

API Evangelist enhancements for Sensors Portal Identity (v2)

5 actions 5 updates documentation extends openapi/sensors-data-portal-identity-v2-openapi.yml
Derived by API Evangelist Built from the contracts Sensors Data publishes. Sensors Data did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

securitySchemessecuritytagsversionx-api-evangelist-sourcex-api-evangelist-harvested

Targets 4

$.components
$
$.info
$.servers

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for Sensors Portal Identity (v2)
  version: 1.0.0
extends: openapi/sensors-data-portal-identity-v2-openapi.yml
x-generated: '2026-08-13'
x-method: generated
x-source: openapi/_original/1.5.5-portal-Identity-v2-swagger.json
x-note: 'The harvested contract is complete on operations (every operation has an operationId, summary,
  description and response example) but omits three things a machine consumer needs: a declared security
  scheme, tags, and any modelled error status. This overlay records those additions WITHOUT mutating the
  harvested original. The same three gaps are present in all 3 portal specs and in all 29 specs across
  the four products; one overlay is published per product against its largest service rather than 29 near-identical
  copies.'
actions:
- target: $.components
  description: Declare the api-key/sensorsdata-project credentials that the contract currently models
    as ordinary required header parameters.
  update:
    securitySchemes:
      apiKey:
        type: apiKey
        in: header
        name: api-key
        description: Project-scoped Sensors Data API key. Created in Project Settings -> Basic Settings
          -> API Key Management; inherits the permissions of the account it was issued to.
      projectHeader:
        type: apiKey
        in: header
        name: sensorsdata-project
        description: Tenant project selector, required on every call.
- target: $
  description: Apply the api-key scheme globally; it is required on 100% of operations.
  update:
    security:
    - apiKey: []
      projectHeader: []
- target: $
  description: Add a tag for the Identity service so operations can be grouped; the harvested spec declares
    no tags and carries the service name only in x-sd-openapi-service-name.
  update:
    tags:
    - name: Identity
      description: 身份 — 身份服务主要负责管理账号权限相关的接口,例如:账号、角色、权限点资源等
- target: $.info
  description: Record the release train the spec was published under; info.version is empty in the harvested
    original.
  update:
    version: 1.5.5
    x-api-evangelist-source: https://manual.sensorsdata.cn/openapi/api/v1/openapi_download?file_name=1.5.5-portal-Identity-v2-swagger.json
    x-api-evangelist-harvested: '2026-08-13'
- target: $.servers
  description: Explain the relative server path. Sensors Data is deployed per customer, so the host is
    the customer cluster ingress; the harvested servers[] carries the path only.
  update:
  - url: https://{sensors_data_url}/api/v3/portal/v2
    description: Customer cluster entry address. The docs state the access address is the load-balancer
      address or domain name of the customer cluster.
    variables:
      sensors_data_url:
        default: sensors_data_url
        description: Host of the customer-deployed Sensors Data cluster.

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/sensors-data-portal-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.