The APIS Docs
HookDiscordContact Us
  • ☺️Hello, Web3!
  • ↔️About The APIS
    • Introduction
    • Core Team
    • Our Partners
  • 🤖Roadmap
  • 🍦Products
    • 🔍Hook
      • Get Started
        • Explore
        • Calendar
        • Collections Trending
        • Watch List
      • Twitter RSS
      • Chatting /w Community
    • ❄️Data Lake
  • 🤓Academy
    • On-Chain Glossary
      • NFT
      • DeFi
  • ℹ️$API Token Info
    • 🅰️$API Smart Contract Address
    • 🪙Token Economics
      • $API Token Utility
      • $API Token Distribution
      • Dune Analysis
      • Investors
      • FAQs
        • What is API?
        • How do APIs work?
        • What is the API token?
        • Why does API stand out?
        • What does API mean for the crypto industry?
    • 📈Get $API Token
    • ⬆️Listed Exchanges
  • 🤝Get In Touch
    • 🥰Contact Us
    • 🥰Join Us
    • ❓FAQ
  • 📖Docs
    • 🔐Security
      • 📄Security Report by Certik
    • 📄Terms & Conditions
    • 📑Privacy Policy
    • ℹ️Disclaimer
  • 📃Whitepaper
    • Whitepaper
      • 1️⃣1⃣ Background
        • 1.1 Background
        • 1.2 Introduction
      • 2️⃣2⃣ Architecture
        • 2.1 Message Propagation Protocol
        • 2.2 Message Formatting Overview
        • 2.3 APIS Core Contracts
        • 2.4 Governance Contract (GC)
        • 2.5 Dispute Resolution Contract (DRC) Factory
        • 2.6 Optimistic Rollup Contract
      • 3️⃣3⃣ Applications
        • 3.1IDs
        • 3.2 API Token
        • 3.3 Token Distribution, Community Ownership
      • 4️⃣4⃣ Discussion
      • 5️⃣5⃣ Appendix
        • 5.1 REST History and Analysis
        • 5.2 REST APIs in Practice
        • 5.3 Strengths and Weaknesses of REST
        • 5.4 GraphQL History and Analysis
        • 5.5 GraphQL as a ‘Fetching Tree’
        • 5.6 Anatomy of a GraphQL Request
        • 5.7Note on GraphQL Resolvers:
        • 5.8 Direct Comparison
        • 5.9 Weaknesses of GraphQL
      • 6️⃣6⃣ Bibliography
Powered by GitBook
On this page
Edit on GitHub
  1. $API Token Info
  2. Token Economics
  3. FAQs

How do APIs work?

An API is a set of defined code that tell computers or applications to communicate with one another in specifications. APIs sit between web servers, acting as an intermediary layer that processes real-time data transfer between systems.

For a physical metaphor, an API works similarly to how a waiter or waitress acts as an intermediary between the kitchen and customer in a restaurant. The working steps as follow:

  1. A customer visits a restaurant and places an order (A client application initiates a request to retrieve information. This request is processed from an application to the web server via the API’s Uniform Resource Identifier (URI).)

  2. The waiter (our API) translates and relays the order from the customer to the kitchen (After receiving a valid request, the API makes a call to the external program or web server.).

  3. Then, the kitchen prepares the meal, and hands it to waiter (The server sends a response to the API with the requested information).

  4. The waiter delivers it to the customer as requested (The API transfers the data to the initial requesting application.).

When a user visits the website of a SaaS product and log in via a social media account, an API relays that user’s request to the chosen social network (Google, Facebook, Twitter, Github, etc), verifies their identities, and then returns that verification to the back-end services of the application. The APIS is a leading API provider for public blockchain data, both on layer-one main chains (such as Ethereum and Bitcoin) and layer-two scaling solutions (such as Binance Smart Chain, Polygon, and, soon, Arbitrum).

PreviousWhat is API?NextWhat is the API token?

Last updated 3 years ago

ℹ️
🪙