Velo Payments APIs
  1. Users
Velo Payments APIs
  • Login
    • Authentication endpoint
      POST
    • Logout
      POST
    • Reset password
      POST
    • validate
      POST
  • Funding Manager
    • Get Funding Audit Delta
      GET
    • Get Funding Accounts
      GET
    • Get Funding Account
      GET
    • Get list of source accounts
      GET
    • Get details about given source account.
      GET
    • Create Funding Request
      POST
    • Set notifications
      POST
    • Get Funding Accounts
      GET
    • Get Funding Account
      GET
    • Get list of source accounts
      GET
    • Get details about given source account.
      GET
    • Create Funding Request
      POST
    • Transfer Funds between source accounts
      POST
    • Get list of source accounts
      GET
    • Get details about given source account.
      GET
    • Create Funding Request
      POST
    • Transfer Funds between source accounts
      POST
  • Payment Audit Service (Deprecated)
    • V1 List Payment Changes
    • V1 Get Fundings for Payor
    • V1 Get Payout Statistics
    • V3 Get List of Payments
    • V3 Get Payment
    • V3 Get Payouts for Payor
    • V3 Get Payments for Payout
    • V3 Export Transactions
  • Countries
    • List Payment Channel Country Rules
    • List Supported Countries
    • List Supported Countries
  • Payout Service
    • Withdraw a Payment
    • Submit Payout
    • Withdraw Payout
    • Get Payout Summary
    • Instruct Payout
    • Retrieve payments for a payout
    • Create a quote for the payout
  • Payors
    • List Payor Links
    • Get Payor
    • Create Application
    • Create API Key
    • Get Branding
    • Add Logo
    • Reminder Email Opt-Out
    • Get Payor
  • Payors Private
    • Create a Payor Link
  • Webhooks
    • List the details about the webhooks for the given payor.
    • Create Webhook
    • Get details about the given webhook.
    • Update Webhook
    • /v1/webhooks/{webhookId}/ping
  • Currencies
    • List Supported Currencies
  • Funding Manager Private
    • Create Funding Account
    • Delete a source account by ID
  • Users
    • List Users
      GET
    • Invite a User
      POST
    • Register SMS Number
      POST
    • Get Self
      GET
    • Unregister MFA for Self
      POST
    • Update Password for self
      POST
    • Validate the proposed password
      POST
    • Update User Details for self
      POST
    • Delete a User
      DELETE
    • Get User
      GET
    • Disable a User
      POST
    • Enable a User
      POST
    • Unregister MFA for the user
      POST
    • Update User Role
      POST
    • Unlock a User
      POST
    • Update User Details
      POST
  • Tokens
    • Resend a token
  • Payees
    • List Payees
    • List Payee Changes
    • Delete Payee by Id
    • Get Payee by Id
    • Update Payee Details
    • Update Payee Remote Id
    • List Payees
    • List Payee Changes
    • Delete Payee by Id
    • Get Payee by Id
    • Update Payee Details
    • Update Payee Remote Id
  • Payee Invitation
    • Initiate Payee Creation
    • Query Batch Status
    • Get Payee Invitation Status
    • Resend Payee Invite
    • Initiate Payee Creation
    • Query Batch Status
    • Get Payee Invitation Status
    • Resend Payee Invite
  • Payment Audit Service
    • Get Fundings for Payor
    • Get List of Payments
    • Get Payment
    • Get Payout Statistics
    • Get Payouts for Payor
    • Get Payments for Payout
    • Export Transactions
    • List Payment Changes
  1. Users

Unlock a User

Velo Payments Sandbox for testing
https://api.sandbox.velopayments.com/
Velo Payments Sandbox for testing
https://api.sandbox.velopayments.com/
POST
/v2/users/{userId}/unlock
If a user is locked this endpoint will unlock them
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://api.sandbox.velopayments.com//v2/users//unlock'
Response Response Example
204 - Example 1
{}

Request

Path Params

Responses

🟢204Success the user was unlocked or was already unlocked
application/json
Body

🟠400Invalid request. See Error message payload for details of failure
🟠401Invalid access token. May be expired or invalid
🟠403The authentication does not have permissions to access the resource This usually occurs when there is a valid authentication instance (client or user) but they do not have the required permissions
🟠404The resource was not found or is no longer available
Modified at 2022-09-11 21:50:18
Previous
Update User Role
Next
Update User Details
Built with