generated: '2026-07-19'
method: searched
source: https://developer.funnelleasing.com/apis/customer-api/authentication
docs: https://developer.funnelleasing.com/apis/customer-api/authentication
summary:
  types: [http]
  http_schemes: [basic, bearer]
  api_key_in: [basic-auth-username, authorization-header]
  oauth2_flows: []
  transport: HTTPS required
notes: >
  Funnel issues API keys scoped to a customer account. Two key kinds exist:
  public keys for client-side integrations and private keys for server-to-server
  calls (private keys must be kept secret / stored in a secrets manager). The
  Customer API authenticates with HTTP Basic where the username is the API key
  and the password is left blank. The Partner API additionally accepts the API
  key as a Bearer token in the Authorization header.
schemes:
  - name: basicAuth
    type: http
    scheme: basic
    description: >
      HTTP Basic Authentication. The username is your API key and the password
      is blank. Requests must be made over HTTPS.
    example: 'curl --user YOUR_API_KEY: https://api.funnelleasing.com/api/v2/onlineleasing-link/'
    applies_to: [Customer API, Partner API]
    sources: [https://developer.funnelleasing.com/apis/customer-api/authentication]
  - name: bearerAuth
    type: http
    scheme: bearer
    description: >
      Partner API also supports supplying the API key as a Bearer token in the
      Authorization header.
    applies_to: [Partner API]
    sources: [https://developer.funnelleasing.com/apis/partner-api]
key_types:
  - kind: public
    use: client-side integrations
  - kind: private
    use: server-to-server integrations; must be kept secret
auth_responses:
  - status: 200
    meaning: OK — authenticated
  - status: 401
    meaning: Unauthorized — missing or invalid credentials
  - status: 403
    meaning: Forbidden — valid credentials but no access permission