generated: '2026-07-19'
method: searched
source: >-
  Evolv SDK source (evolv-ai/javascript-sdk build-options.js, evolv-ai/android-sdk
  EvolvConfig.java) + developers.evolv.ai Participant API reference
summary:
  types:
  - apiKey
  api_key_in:
  - path
  oauth2_flows: []
schemes:
- name: environmentId
  type: apiKey
  in: path
  description: >-
    The Participant API is keyed by a public environment id embedded in the request URL
    path (https://participants.evolv.ai/v1/{environment}/...). The environment id scopes
    all configuration, allocation, and event-ingestion requests to a specific Evolv
    project/environment. It is a publishable (client-side) key delivered in the browser
    or mobile app snippet.
  sources:
  - evolv-ai/android-sdk EvolvConfig.java (DEFAULT_ENDPOINT https://participants.evolv.ai/v1)
- name: participantUid
  type: apiKey
  in: path
  description: >-
    A participant/visitor identifier (uid), and optionally a session id (sid), are passed
    in the request path to fetch that participant's allocations and to attribute ingested
    events. Identity is managed by the SDK, not an account credential.
  sources:
  - evolv-ai/javascript-sdk src/index.js
notes: >-
  The runtime Participant API uses no OAuth or bearer token — access is by public
  environment id plus participant uid over HTTPS. Management/authoring of experiments
  (via the Evolv app and the experiment-management-cli) is performed against the
  authenticated Evolv account, separate from this runtime edge API. No OpenAPI is
  published, so this profile is derived from the official SDK source rather than a spec.