EDDA Technology · Authentication Profile

Edda Authentication

Authentication

EDDA Technology secures its APIs with none and http across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyHealth TechMedical ImagingRadiologySurgeryOncologyArtificial IntelligenceMedical DevicesHealthcareClinical Software
Methods: none, http Schemes: 2 OAuth flows: API key in:

Security Schemes

anonymous none
applicationPassword http
scheme: basic

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://www.eddatech.com/wp-json/
docs: https://www.eddatech.com/wp-json/
summary:
  types:
  - none
  - http
  api_key_in: []
  oauth2_flows: []
  anonymous_read: true
  notes: >-
    EDDA Technology publishes no developer-facing authentication program. The only public HTTP API
    surface is the WordPress REST API on www.eddatech.com, whose entire public read surface
    (posts, pages, media, taxonomies, search, oEmbed) is served anonymously with no credential.
    The API root advertises exactly one authentication mechanism — WordPress application passwords
    (HTTP Basic) — which gates write operations and administrative routes and is not offered to
    third-party developers. There is no OAuth 2.0, no OpenID Connect, no API-key program and no
    developer key issuance, so scopes/ is intentionally absent.
schemes:
- name: anonymous
  type: none
  description: >-
    All read operations catalogued in openapi/edda-wordpress-openapi.yml return 200 with no
    Authorization header. Verified live 2026-07-20.
  sources:
  - openapi/edda-wordpress-openapi.yml
- name: applicationPassword
  type: http
  scheme: basic
  description: >-
    WordPress application passwords (HTTP Basic: username + application password). Advertised by the
    API root at https://www.eddatech.com/wp-json/ under authentication.application-passwords.
    Credentials are issued per WordPress user account by the site administrator, not through a public
    developer program. Required only for write operations and non-public routes.
  authorization_endpoint: https://www.eddatech.com/wp-admin/authorize-application.php
  accepted_headers:
  - Authorization
  - X-WP-Nonce
  applies_to: write operations and non-public routes (e.g. /wp/v2/settings, /mpdl/downloads/files)
  sources:
  - https://www.eddatech.com/wp-json/
  - openapi/edda-wordpress-openapi.yml
observed:
- request: GET https://www.eddatech.com/wp-json/wp/v2/posts?per_page=1
  auth: none
  status: 200
- request: GET https://www.eddatech.com/wp-json/wp/v2/settings
  auth: none
  status: 401
  body: '{"code":"rest_forbidden","message":"Sorry, you are not allowed to do that.","data":{"status":401}}'
- request: GET https://www.eddatech.com/wp-json/mpdl/downloads/files
  auth: none
  status: 401