> ## Documentation Index
> Fetch the complete documentation index at: https://docs.range.org/llms.txt
> Use this file to discover all available pages before exploring further.

# List the Wise profiles a token can reach

> Returns the profiles reachable with a read-only Wise API token, so the connect form can ask the user which one to connect. A Wise connection is keyed on a profile id, so this runs before any connection exists and takes the token in the body; the token is used for this request only and is never stored. This must be called server-side rather than from a browser: Wise sends no CORS headers, and resolving the list here guarantees it comes from the same Wise host and API version that credential validation will use. Pass the chosen id back as `wise.profile_id` on POST /account-connections.



## OpenAPI

````yaml /api-reference/platform-api.json post /v2/account-connections/wise/profiles
openapi: 3.0.0
info:
  title: Range Platform API
  description: >-
    The Range Platform API for workspace management, counterparties, and
    operational tooling.
  version: 1.7.16
  contact: {}
servers:
  - url: https://api.range.org
    description: Range API Server
security:
  - Authorization: []
  - Authorization: []
tags:
  - name: Address Information
    description: Get information about a crypto address.
  - name: Transfer Enrichments
    description: Attach workspace-scoped notes and categories to transfers.
  - name: Counterparties
    description: Manage external entities, their addresses, bank accounts, and documents.
paths:
  /v2/account-connections/wise/profiles:
    post:
      tags:
        - Account Connections
      summary: List the Wise profiles a token can reach
      description: >-
        Returns the profiles reachable with a read-only Wise API token, so the
        connect form can ask the user which one to connect. A Wise connection is
        keyed on a profile id, so this runs before any connection exists and
        takes the token in the body; the token is used for this request only and
        is never stored. This must be called server-side rather than from a
        browser: Wise sends no CORS headers, and resolving the list here
        guarantees it comes from the same Wise host and API version that
        credential validation will use. Pass the chosen id back as
        `wise.profile_id` on POST /account-connections.
      operationId: listWiseProfiles
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ListWiseProfilesDto'
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListWiseProfilesResponseDto'
components:
  schemas:
    ListWiseProfilesDto:
      type: object
      properties:
        api_token:
          type: string
          description: >-
            A read-only Wise API token. Used for this request only and never
            stored — persisting it happens later, when POST /account-connections
            creates the connection.
          example: 00000000-0000-0000-0000-000000000000
      required:
        - api_token
    ListWiseProfilesResponseDto:
      type: object
      properties:
        items:
          type: array
          items:
            $ref: '#/components/schemas/WiseProfileOptionDto'
      required:
        - items
    WiseProfileOptionDto:
      type: object
      properties:
        id:
          type: string
          description: >-
            The Wise profile id, as a string. Pass it back as `wise.profile_id`
            when creating the connection.
          example: '12345678'
        type:
          type: string
          description: >-
            The profile kind. 'OTHER' covers any kind Wise introduces that this
            API does not yet recognise, so clients should render such a profile
            by name alone rather than assuming it is personal.
          enum:
            - PERSONAL
            - BUSINESS
            - OTHER
          example: BUSINESS
        name:
          type: string
          nullable: true
          description: >-
            A display name for the profile: the company name for a business
            profile, the account holder for a personal one. Null when Wise
            returns no name, in which case clients should show the id.
          example: Range Security Ltd
      required:
        - id
        - type
        - name
  securitySchemes:
    Authorization:
      type: apiKey
      in: header
      name: X-API-KEY
      description: Authorization method required to allow user to access the api endpoints.

````