Anvyl · Authentication Profile

Anvyl Authentication

Authentication

No public OpenAPI/Swagger document is exposed by Anvyl (developer docs are served as a gated Stoplight SPA), so the auth model here is captured from observed live behavior rather than derived from a spec. Unauthenticated requests to the REST API return HTTP 401 with {"error":"Unauthorized"}. A request carrying an Authorization: Bearer header passes the auth gate (the same route then returns 404 for an unknown token context rather than 401), whereas an X-API-Key header does not (still 401) — indicating the API authenticates with a bearer token in the standard Authorization header.

Anvyl secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyLogisticsSupply ChainProcurementPurchase OrdersManufacturingProduction Management
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer · in: header ()

Source

Authentication Profile

anvyl-authentication.yml Raw ↑ 
generated: '2026-07-17'
method: searched
source: >-
  Live probe of https://api.anvyl.com/api/v1 plus the Anvyl developer
  documentation at https://anvyl.stoplight.io/docs/anvyl-api
description: >-
  No public OpenAPI/Swagger document is exposed by Anvyl (developer docs are
  served as a gated Stoplight SPA), so the auth model here is captured from
  observed live behavior rather than derived from a spec. Unauthenticated
  requests to the REST API return HTTP 401 with {"error":"Unauthorized"}. A
  request carrying an Authorization: Bearer <token> header passes the auth gate
  (the same route then returns 404 for an unknown token context rather than
  401), whereas an X-API-Key header does not (still 401) — indicating the API
  authenticates with a bearer token in the standard Authorization header.
summary:
  types: [http]
  http_schemes: [bearer]
  api_key_in: []
  oauth2_flows: []
schemes:
  - name: bearerAuth
    type: http
    scheme: bearer
    in: header
    header: Authorization
    description: >-
      Bearer token supplied in the Authorization header
      (Authorization: Bearer <token>). Tokens are provisioned via the Anvyl
      platform's API access feature; see the developer docs for issuance.
    evidence:
      - "GET https://api.anvyl.com/api/v1 without auth -> 401 {\"error\":\"Unauthorized\"}"
      - "GET https://api.anvyl.com/api/v1/purchase_orders with Authorization: Bearer <bogus> -> 404 (past the 401 gate)"
      - "GET https://api.anvyl.com/api/v1/purchase_orders with X-API-Key: <bogus> -> 401 (header not honored)"
    sources:
      - live probe
docs: https://anvyl.stoplight.io/docs/anvyl-api

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/anvyl-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.

GitHub Google LinkedIn

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