LogoLogo
  • Welcome to Alterscope
  • INTRODUCTION
    • What is DefAI?
    • What are AI Agents?
    • What is Alteron?
  • How to get started
    • Sign Up
    • Agent Framework
    • Agent Signals
      • APY Changes
      • Arbitrage Opportunities
      • Centralised Exchange Movements
      • Cyvers Security Alerts
      • DAO Proposals
      • Ecosystem In/Out-Flows
      • ERC20 Price Movements
      • Function Calls
      • Gas Fee Spikes
      • Protocol Health Alerts
      • Simple Moving Averages
      • Stablecoin Price Deviations
      • Token Transfers
      • Wallet Health Factors
      • Whale Activity
    • Agent Network
  • Data Feeds
    • API Endpoint
    • Authentication
    • API Reference
      • Development
      • Development Score
      • Security
      • Liquidity
        • Lending Protocols
        • Decentralized Exchange Protocols
        • Stablecoin Protocols
        • Derivative Protocols
        • Liquid Staking Protocols
      • Community
      • Governance
      • Governance Score
      • Blockchain
      • Oracles
      • Overall Score
      • Tokenomics
      • Tokenomics Score
      • Restaking
    • Swagger API Specification
    • Install & run cURL on Windows/MacOSX/Linux
  • Dashboard Functionalities
    • Market Insights
    • Custom API Creation (Nexus)
    • Custom Dashboards (Eagle Eye)
Powered by GitBook
On this page
  1. Data Feeds

Authentication

Get your Access Token

The Alterscope API relies on personal access tokens for request authentication.

To acquire your access token, ensure that you are a participant. If you are a participant, kindly check your email for the access token sent by our team! All API requests undergo authentication using the Bearer Auth scheme. To authenticate a request, include the token in the Authorization header as follows: Sample Request for Authorization:

curl https://api.alterscope.org/authorization -H "Authorization: Bearer <your_access_token>"

Exercise caution and maintain the security of your API access tokens! Avoid sharing them in emails, chat messages, client-side code, or on publicly accessible sites. In the event of sharing an API access token publicly, promptly email us to initiate its revocation process.

Sample Valid Response:

{"status":true,"data":"Authorization token is valid. Successfully authorized"} 

Sample Invalid Response:

{"error":"Invalid Authorization header"}
PreviousAPI EndpointNextAPI Reference

Last updated 1 year ago