Muse Finance Authentication

generated: '2026-07-20'
method: searched
source: https://api-docs.getmymuse.com/docs/authentication
docs: https://api-docs.getmymuse.com/docs/authentication
description: >-
  Muse Finance API authentication. Every request must carry TWO credentials: a
  JWT bearer token in the Authorization header AND a static API key in the
  x-api-key header. Partners are issued an API key, Client ID and Client Secret
  by Muse (via technical-support@getmymuse.com), then exchange those for a
  short-lived JWT through a designated token-exchange endpoint before calling
  the API.
summary:
  types: [http, apiKey]
  api_key_in: [header]
  http_schemes: [bearer]
  bearer_format: JWT
  credential_issuance: manual (contact technical-support@getmymuse.com)
schemes:
  - name: bearerAuth
    type: http
    scheme: bearer
    bearer_format: JWT
    in: header
    header: Authorization
    value_prefix: 'Bearer '
    description: >-
      Short-lived JWT obtained by exchanging the issued API key + Client ID +
      Client Secret at the designated token-exchange endpoint.
    sources: [docs]
  - name: apiKeyAuth
    type: apiKey
    in: header
    parameter_name: x-api-key
    description: Static partner API key, issued by Muse Finance support.
    sources: [docs]
example_request: |
  curl -H "Authorization: Bearer YOUR_JWT_TOKEN" \
       -H "x-api-key: YOUR_API_KEY" \
       https://<api-host>/applications
notes:
  - Both headers are required on every request.
  - No OAuth 2.0 scopes are documented; access is partner-scoped by credential.
  - The production API base host is not published in the public docs; issued to partners on onboarding.