DAS Technology · OpenAPI Overlay 1.0.0

API Evangelist enhancements for DASWebAPI V2

5 actions 5 updates documentation extends openapi/das-technology-daswebapi-v2-openapi.yml
Derived by API Evangelist Built from the contracts DAS Technology publishes. DAS Technology did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

descriptioncontactsecurityDefinitionssecuritydefinitionsresponsesx-conventions

Targets 3

$.info
$
$.paths[*][?(@.operationId)]

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for DASWebAPI V2
  version: 1.0.0
  x-description: 'Non-destructive enhancements to the Swagger 2.0 document DAS Technology publishes at https://api.digitalairstrike.com/swagger/docs/v2.
    The upstream document is left byte-for-byte intact in openapi/_original/. Every action below encodes
    something OBSERVED (a live 401 carrying WWW-Authenticate: Bearer, live 404/500 error bodies) or something
    the document is missing that a machine consumer needs. Nothing here invents an operation, a parameter
    or a schema.'
  x-generated: '2026-08-12'
  x-method: generated
  x-source: openapi/_original/das-technology-daswebapi-v2-swagger.json
  x-operations: 32
extends: openapi/das-technology-daswebapi-v2-openapi.yml
actions:
- target: $.info
  description: Record the human documentation surface and the maintaining brand — the document ships with
    only a title and version.
  update:
    description: DASWebAPI V2. Published by DAS Technology (formerly Digital Air Strike) as a Swashbuckle-generated
      Swagger 2.0 document at https://api.digitalairstrike.com/swagger/docs/v2 and rendered at https://api.digitalairstrike.com/swagger.
      All operations require a bearer token; DAS Technology publishes no developer portal, so token issuance
      is arranged through the dealer/OEM/partner relationship.
    contact:
      name: DAS Technology
      url: https://www.dastechnology.com
- target: $
  description: 'Declare the bearer scheme the API actually enforces. Probed 2026-08-12: an anonymous request
    to any resource returns 401 with WWW-Authenticate: Bearer. The upstream document declares no securityDefinitions
    at all, so generated clients emit unauthenticated calls.'
  update:
    securityDefinitions:
      bearerAuth:
        type: apiKey
        name: Authorization
        in: header
        description: 'Bearer token: `Authorization: Bearer <token>`. Observed on a live 401 (WWW-Authenticate:
          Bearer). Token issuance is not publicly documented.'
    security:
    - bearerAuth: []
- target: $
  description: Add the error envelope observed on the wire. The upstream document declares only 200 on
    all operations and defines no error schema.
  update:
    definitions:
      DAS.Error:
        type: object
        description: Proprietary XML/JSON error envelope returned by the DAS Web API. Observed on live
          401 and 500 responses. Note that 404 is returned as an ASP.NET HTML page, not as this envelope.
        properties:
          Message:
            type: string
            description: Human-readable error message.
          ExceptionMessage:
            type: string
            description: Present on unhandled server faults only.
          ExceptionType:
            type: string
            description: Present on unhandled server faults only.
          StackTrace:
            type: string
            description: Present on unhandled server faults only. Verbose disclosure — see errors/das-technology-problem-types.yml.
- target: $.paths[*][?(@.operationId)]
  description: Attach the 401 and 500 responses every operation can return but none documents.
  update:
    responses:
      '401':
        description: Unauthorized — missing or rejected bearer token. Body is application/xml <Error><Message>Authorization
          has been denied for this request.</Message></Error>. Probed 2026-08-12.
        schema:
          $ref: '#/definitions/DAS.Error'
      '500':
        description: Internal server error. Body is application/xml and currently includes ExceptionType
          and a full StackTrace.
        schema:
          $ref: '#/definitions/DAS.Error'
- target: $
  description: Record cross-cutting runtime semantics an agent needs and the contract omits.
  update:
    x-conventions:
      idempotency:
        supported: false
        note: No Idempotency-Key header. Non-GET operations (email send, SMS provisioning, survey dispatch,
          SOCi provisioning) double-fire on retry.
      rate_limits:
        published: false
        headers: []
        note: No RateLimit-*/Retry-After header observed.
      request_id:
        header: null
        note: No request or correlation identifier is returned.
      error_media_type: application/xml
      artifacts:
        authentication: authentication/das-technology-authentication.yml
        conventions: conventions/das-technology-conventions.yml
        errors: errors/das-technology-problem-types.yml
        lifecycle: lifecycle/das-technology-lifecycle.yml
        rate_limits: rate-limits/das-technology-rate-limits.yml
        data_model: data-model/das-technology-data-model.yml

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/das-technology-daswebapi-v2-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.