🇬🇧
Yativo Documentation
Spanish
English
English
  • Yativo
  • Introduction to Yativo
    • Financial Infrastructure
    • About Us
  • Dashboard
  • Business Plans
  • Getting Started with Yativo API
  • Yativo API Glossary
  • API reference
    • Misc.
      • Countries
      • States
      • City
  • Security and Authentication
    • Security
    • Authentication
    • Idempotency in API Requests
  • Environment
    • Environments
  • Notifications
    • Webhook
  • Compliance
    • Verification
      • KYC
      • KYB
      • KYC/KYB Update
      • KYC Status
      • Global Business Search
    • Supported Jurisdiction
    • Supported Countries, Currencies and Payment Method
  • User Management
    • Customer
      • Get Customers
      • Retrieve customer
      • Add Customer
  • Payments
    • Currencies
    • Crypto Wallets
      • Generate Wallet Address
      • Fetch Wallet Address
      • Crypto Deposit History
      • Single crypto deposit history
    • Payout
      • Payout
      • Get Payouts
      • Get Payout
      • Beneficiaries
        • Get Beneficiaries
        • Add Beneficiary Payment Details
        • Update Beneficiary
        • Archive Beneficiary
        • Add Beneficiary
    • Payin
    • Virtual Cards
      • Supported Currency, Country
      • Create card
      • Fetch card
      • Top up card
      • Get Transactions
      • Freeze and Unfreeze Card
    • Virtual Accounts
      • Create VIrtual Accounts
        • USD Virtual Account
        • Mexico Virtual Account
        • Brazil PIX QR
      • Virtual Account Management
      • Transaction History
  • Foreign Exchange
    • Exchange Rate
      • Request Quote
  • Transactions
    • Transaction Summary
    • Get Single Transaction
  • Crypto System
    • Yativo Crypto Platform API
Powered by GitBook
On this page
  1. Crypto System

Authentication

Overview

Authentication is the starting point for any integration with the Yativo Crypto Platform. All API requests must include a bearer token obtained through the authentication process.

Use Case

  • Login Flow: Your system authenticates itself with Yativo by providing valid credentials, receives a bearer token, and uses this token to access other endpoints.

  • Two-Factor Authentication (2FA): Add an additional layer of security with Google Authenticator verification.

Endpoints

Login

  • URL: POST /api/authentication/login

  • Description: Use this endpoint to log in and obtain an access token.

  • Implementation Context:

    • Useful for creating an admin panel or backend system for managing wallets and transactions.

    • Should be called before performing any other API operations.

  • Request Example:

  • {
        "email": "user@example.com",
    }
  • Response Example:

  • {
        "status": "success",
        "token": "eyJhbGciOiJIUzI1NiIs..."
    }

Verify Google Authenticator

  • URL: POST /api/authentication/google_auth_verification

  • Description: Confirms the user's identity through an OTP provided by Google Authenticator.

  • Implementation Context:

    • Protect sensitive endpoints like withdrawals or account changes.

    • Ideal for users managing multiple high-value wallets.

  • Request Example:

  • {
        "email": "user@example.com",
        "otp": "123456"
    }
  • Response Example:

  • {
        "status": "verified",
        "message": "Authentication successful"
    }

Last updated 2 months ago