YAZIO · Authentication Profile

Yazio Authentication

Authentication

YAZIO declares 0 security scheme(s) across its OpenAPI definitions.

CompanyHealthDigital HealthNutritionCalorie TrackingWeight ManagementIntermittent FastingFitnessConsumer HealthMobile ApplicationsGermany
Methods: Schemes: 0 OAuth flows: API key in:

Security Schemes

Source

Authentication Profile

yazio-authentication.yml Raw ↑
generated: '2026-08-27'
method: probed
source: >-
  live unauthenticated requests to https://yzapi.yazio.com, 2026-08-27
  (GET /v15/user, GET /v14/user, POST /v15/oauth/token)
documented: false
pointer_withheld: >-
  No `type: Authentication` pointer is wired into apis.yml. The scoring check it
  feeds is `authentication_documented`, and YAZIO documents none of this — every
  field below was read off a live error response, not off a published auth page.
  Wiring the pointer would credit YAZIO with documentation it has never shipped.
summary: >-
  YAZIO's application backend is OAuth 2.0 with a resource-owner-password-credentials
  grant that additionally requires a confidential client id and secret. The token
  endpoint's own validation error, returned to an anonymous POST, names the four
  required fields. Every resource endpoint probed answers 401 to an anonymous
  request. None of this is published by YAZIO; it is observable only by calling the
  host the mobile apps call.
security_schemes:
- name: oauth2_password
  type: oauth2
  flow: password
  token_endpoint: https://yzapi.yazio.com/v15/oauth/token
  content_type: application/x-www-form-urlencoded
  required_parameters:
  - username
  - password
  - client_id
  - clientSecret
  - grant_type
  evidence:
    url: https://yzapi.yazio.com/v15/oauth/token
    method: POST
    http_status: 400
    body_excerpt: >-
      [{"property_path":"","message":"Invalid client"},{"property_path":"username",
      "message":"This value should not be blank."},{"property_path":"password",
      "message":"This value should not be blank."},{"property_path":"clientSecret",
      "message":"This value should not be blank."}]
  note: >-
    Client credentials are not issuable by any public YAZIO process — there is no
    developer signup, no application registration and no client-id request form.
    The credentials in circulation are the ones extracted from the shipped mobile
    apps by third parties.
- name: bearer
  type: http
  scheme: bearer
  applied_to: all probed resource endpoints
  evidence:
    url: https://yzapi.yazio.com/v15/user
    method: GET
    http_status: 401
scopes: null
scopes_note: >-
  No scope surface was observable and none is documented. scopes/ is therefore not
  emitted rather than emitted empty.
versions_observed:
- v14
- v15

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact 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 security artifact
curl "https://apis.io/api/v1/security/yazio-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.