Artillery · Authentication Profile
Artillery Authentication
Authentication
Artillery secures its APIs with apiKey across 2 declared security schemes, as derived from its OpenAPI definitions.
Load TestingPerformance TestingOpen-SourceTestingDevOpsNode.js
Methods: apiKey
Schemes: 2
OAuth flows:
API key in: cli-flag, environment-variable, header
Security Schemes
ArtilleryCloudApiKey apiKey
· in: cli-flag (--key)
ArtilleryCloudSessionToken http
scheme: bearer
· in: header ()
Source
Authentication Profile
generated: '2026-09-07'
method: searched
source: >-
https://www.artillery.io/docs/reference/stash, https://www.artillery.io/docs/reference/cli/run,
https://www.artillery.io/pricing, https://www.artillery.io/changelog, plus live anonymous
probes of https://app.artillery.io/api
docs: https://www.artillery.io/docs/reference/cli/run
note: >-
DERIVED FROM DOCS AND LIVE PROBES, NOT FROM A SPEC — Artillery publishes no OpenAPI, so there
are no securitySchemes to aggregate. What is recorded below is what the provider documents
and what the live endpoint actually answers.
summary:
types: [apiKey]
api_key_in: [cli-flag, environment-variable, header]
oauth2_flows: []
federation: [oidc, saml]
provisioning: [scim]
schemes:
- name: ArtilleryCloudApiKey
type: apiKey
in: cli-flag
parameter: --key
alt_parameter: ARTILLERY_CLOUD_API_KEY
key_prefix: a9_
key_prefix_evidence: >-
https://www.artillery.io/docs/reference/stash — published example
"ARTILLERY_CLOUD_API_KEY=a9_yourApiKey node seed-data.ts"
obtained_from: Artillery Cloud dashboard settings at https://app.artillery.io
used_by:
- artillery run --record --key <key> (record a test run to Artillery Cloud)
- Stash API (persistent key-value store; client auto-configured from the same key)
- '@artilleryio/playwright-reporter (Playwright E2E reporting into Artillery Cloud)'
sources: [docs]
- name: ArtilleryCloudSessionToken
type: http
scheme: bearer
in: header
observed: true
observation: >-
Anonymous requests to any path under https://app.artillery.io/api return HTTP 401 with the
body {"error":{"data":{"message":"Missing auth token","code":401,"type":"ServerError"}}}.
The token name and format are not published; the Cloud API is an undocumented,
authenticated-only surface.
sources: [live probe 2026-09-07]
federation:
- name: Enterprise SSO
protocols: [oidc, saml]
provisioning: scim
self_service: true
evidence: >-
Pricing page lists "Enterprise SSO (OIDC & SAML), audit logs, custom MSA, and support SLAs"
as an add-on from $1199/month; the changelog entry of 2026-07-29 announces self-service SSO
and SCIM onboarding from Settings -> SSO in Artillery Cloud.
docs: https://www.artillery.io/pricing
public_surface_note: >-
There is no anonymous or public-read surface on the Artillery Cloud API. Everything an agent
or integrator can do without credentials is documentation: /llms.txt, the .md docs mirror, the
public GitHub org, and the npm packages.
x-evidence:
fetched: '2026-09-07'
probes:
- {url: 'https://app.artillery.io/api/openapi.json', status: 401}
- {url: 'https://app.artillery.io/api/graphql', status: 401}
- {url: 'https://www.artillery.io/docs/reference/stash', status: 200}
- {url: 'https://www.artillery.io/pricing', status: 200}
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.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/artillery-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.