Pico · Authentication Profile

Pico Authentication

Authentication

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

CompanyCreator EconomyCRMMembershipsPaymentsEmail MarketingNewslettersMonetizationRetired
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

apiKey apiKey
· in: header (X-Api-Key)

Source

Authentication Profile

pico-authentication.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://help.trypico.com/en/articles/5632118-using-the-pico-api
docs: https://docs.trypico.com/
summary:
  types:
  - apiKey
  api_key_in:
  - header
schemes:
- name: apiKey
  type: apiKey
  in: header
  parameter: X-Api-Key
  description: >-
    Every request to the Pico API must include an X-Api-Key header carrying an
    API access token. Tokens are generated in the Pico dashboard under
    Settings > Website by clicking "Request access token". No OAuth or scope
    surface is documented; access is a single account-level API key.
  sources:
  - https://help.trypico.com/en/articles/5632118-using-the-pico-api
x-status: historical
x-status-note: >-
  Re-probed 2026-08-13: this is now a HISTORICAL record, not a live auth contract.
  The source article at help.trypico.com returns 403, the API reference at
  docs.trypico.com returns an S3 "NoSuchBucket" 404, and the API host
  api.trypico.com is NXDOMAIN. Pico rebranded to Hype and was acquired by MMA.inc in
  February 2026; the API was withdrawn with it. Retained as the last captured
  description of how the Pico API authenticated. See lifecycle/pico-lifecycle.yml.