# Profiles

A profile represents an identity that can send and receive money through Wise — either a personal profile (an individual) or a business profile (a company). Most API endpoints require a `profileId` parameter, which is the ID of either profile type.

 - [Profile](https://docs.wise.com/api-reference/preview/profile/profile.md): Schema: #/components/schemas/profile
 - [GET /profiles](https://docs.wise.com/api-reference/preview/profile/profilelist.md): List of all profiles belonging to user.
 - [POST /profiles/personal-profile](https://docs.wise.com/api-reference/preview/profile/profilepersonalcreate.md): Create a personal profile for the authenticated user. A personal profile represents an individual and is required before creating transfers or business profiles. Use the `X-idempotence-uuid` header to
 - [POST /profiles/business-profile](https://docs.wise.com/api-reference/preview/profile/profilebusinesscreatev3.md): Creates the business profile and its authorized representative in a single request. This request accepts an optional field in the header, `X-idempotence-uuid`. This should be unique for each Profile y
 - [GET /profiles/{profileId}](https://docs.wise.com/api-reference/preview/profile/profileget.md): Get profile info by ID.
 - [PUT /profiles/{profileId}/personal-profile](https://docs.wise.com/api-reference/preview/profile/profilepersonalupdate.md): Update user profile information for a personal profile. If user profile has been verified then there are restrictions on what information is allowed to change. Where permitted, use the update window f
 - [PUT /profiles/{profileId}/business-profile](https://docs.wise.com/api-reference/preview/profile/profilebusinessupdate.md): Update user profile information for a business profile. If user profile has been verified then there are restrictions on what information is allowed to change. Where permitted, use the update window f
 - [GET /profiles/{profileId}/business-profile/business-representative](https://docs.wise.com/api-reference/preview/profile/profilebusinessrepresentativeget.md): Get Business Representative info by Business Profile ID.
 - [PUT /profiles/{profileId}/business-profile/business-representative](https://docs.wise.com/api-reference/preview/profile/profilebusinessrepresentativeupdate.md): Update or transfer the Business Representative for the specified Business Profile. Set `updateContext` to `UPDATE_DETAILS` to update the existing Business Representative's details, or `TRANSFER_OF_AUT
 - [POST /profiles/{profileId}/verification-documents](https://docs.wise.com/api-reference/preview/profile/profileverificationdocumentcreate.md): Add an identification document to a personal profile. Not applicable to business profiles. For SSN submissions, only `type` and `uniqueIdentifier` (9 digits, no letters or symbols) are required.
 - [PUT /profiles/{profileId}/verification-documents](https://docs.wise.com/api-reference/preview/profile/profileverificationdocumentupdate.md): Update an existing identification document on a personal profile. Not applicable to business profiles. This endpoint performs a full replacement of the document details. Any fields not provided in th
 - [POST /profiles/{profileId}/directors](https://docs.wise.com/api-reference/preview/profile/profiledirectorcreate.md): Adds new directors to the business profile. Returns the list of all directors associated with the business profile.
 - [GET /profiles/{profileId}/directors](https://docs.wise.com/api-reference/preview/profile/profiledirectorlist.md): Returns the list of director objects associated with the business profile.
 - [PUT /profiles/{profileId}/directors](https://docs.wise.com/api-reference/preview/profile/profiledirectorupdate.md): Overrides directors in the business profile. Returns the list of all directors associated with the business profile.
 - [POST /profiles/{profileId}/ubos](https://docs.wise.com/api-reference/preview/profile/profileubocreate.md): Adds new ultimate beneficial owners to the business profile. Returns the list of all ultimate beneficial owners associated with the business profile. All the shareholders that have at least 25% owners
 - [GET /profiles/{profileId}/ubos](https://docs.wise.com/api-reference/preview/profile/profileubolist.md): Returns the list of all ultimate beneficial owners associated with the business profile.
 - [PUT /profiles/{profileId}/ubos](https://docs.wise.com/api-reference/preview/profile/profileuboupdate.md): Replaces the entire collection of ultimate beneficial owners in the business profile. Returns the list of all ultimate beneficial owners associated with the business profile.
 - [POST /profiles/{profileId}/update-window](https://docs.wise.com/api-reference/preview/profile/profileupdatewindowopen.md): Opens the update window for updating the profile information: details, addresses, directors, owners, others.
 - [DELETE /profiles/{profileId}/update-window](https://docs.wise.com/api-reference/preview/profile/profileupdatewindowclose.md): Deletes the update window for updating the profile.
 - [POST /profiles/{profileId}/verification-status/bank-transfer](https://docs.wise.com/api-reference/preview/profile/profileverificationstatuscheck.md): You can check the verification status of a profile using this API. This is a profile-specific API resource which should be accessed using an access token acquired for the profile. We do not expose an
 - [POST profiles#overdraft-limit-threshold](https://docs.wise.com/api-reference/preview/profile/eventprofilesoverdraftlimitthreshold.md): Triggered when the overdraft limit usage has reached 70% threshold. The event at each threshold is triggered maximum once per hour. * Event type: `profiles#overdraft-limit-threshold` * Profile level s
 - [POST profiles#state-change](https://docs.wise.com/api-reference/preview/profile/eventprofilesstatechange.md): Triggered every time a profile's state is updated. * Event type: `profiles#state-change` * Profile level subscriptions: Not Supported * Application level subscriptions: Supported Events may not be de
 - [POST profiles#verification-state-change](https://docs.wise.com/api-reference/preview/profile/eventprofilesverificationstatechange.md): Triggered when the verification state of a connected profile changes. A profile's *verification state* can be `verified` or `not_verified`. - If the state is `verified`, then the user is ready to make