RuBaRu Whitepaper
Main Website
  • Abstract
  • RuBaRu - Why & What?
    • Portal
    • Problem Statement
    • What future holds for Social Media and Content Platforms?
    • Why RuBaRu?
    • Key Stakeholders
    • Core Components of Protocol
      • Fully OnChain Profile, Social Graph & Interactions
      • Decentralized Identity(DiD)
      • Fully On-Chain Rich Media Cloud: Decentralized Storage & Streaming
      • Incentive Program
      • Decentralized Creator Economy
      • Creator/Influencer Reputation Factor
      • Decentralized AI (#DeAi) Layer
      • Content Moderation
      • Brand Positioning
      • DAO Governance
    • Economy
      • Creator-Consumer Incentive Program (CCIP)
        • Join-2-Earn
        • Post-2-Earn
        • Refer-2-Earn
        • Engage-2-Earn
        • Advocate-to-Earn
        • Viral-to-Earn
        • Moderate-to-Earn
      • Creator Monetisation
      • Platform Monetisation
    • Technical Architecture & Breakthroughs
      • High level Architecture Overview
      • On-Chain Social Graph
      • On-Chain Authentication & Identity Layer
      • On-Chain Media & Content Infrastructure Layer(CDN)
      • On-Chain Feed Generation, Recommendation & Delivery Pipeline
      • OnChain Reward Wallet & Transaction Layer
      • On-Chain Content Indexer & Search Layer
      • On-Chain Referral Service
      • Decentralised AI Service layer
      • On-Chain Notification Layer
      • User Experience & Interface Layer (Frontend)
      • Off-Chain Components
        • Push Notification Broker Engine (Off-Chain)
        • Leaderboard Reverse Oracle Service
    • Tokenomics
      • Distribution Model
      • Token Utility
        • Credits : In-App Currency
        • $TOKEN (Governance & Value Capture Token)
      • Airdrop Season#1
      • Airdrop Season#2
    • Marketing & Go-To-Market Strategy
    • Try RuBaRu DApp
    • Roadmap
    • Community
    • Conclusion
    • Disclaimer
    • Quickstart
    • Publish your docs
  • Basics
    • Editor
    • Markdown
    • Images & media
    • Interactive blocks
    • OpenAPI
    • Integrations
Powered by GitBook
On this page
  1. Basics

OpenAPI

PreviousInteractive blocksNextIntegrations

You can sync GitBook pages with an OpenAPI or Swagger file or a URL to include auto-generated API methods in your documentation.

OpenAPI block

GitBook's OpenAPI block is powered by , so you can test your APIs directly from your docs.

Scalar
  • OpenAPI block
  • POSTAdd a new pet to the store.

Add a new pet to the store.

post

Add a new pet to the store.

Authorizations
Body
idinteger · int64OptionalExample: 10
namestringRequiredExample: doggie
photoUrlsstring[]Required
statusstring · enumOptional

pet status in the store

Possible values:
Responses
200
Successful operation
400
Invalid input
422
Validation exception
default
Unexpected error
post
POST /api/v3/pet HTTP/1.1
Host: 
Content-Type: application/json
Accept: */*
Content-Length: 133

{
  "id": 10,
  "name": "doggie",
  "category": {
    "id": 1,
    "name": "Dogs"
  },
  "photoUrls": [
    "text"
  ],
  "tags": [
    {
      "id": 1,
      "name": "text"
    }
  ],
  "status": "available"
}
{
  "id": 10,
  "name": "doggie",
  "category": {
    "id": 1,
    "name": "Dogs"
  },
  "photoUrls": [
    "text"
  ],
  "tags": [
    {
      "id": 1,
      "name": "text"
    }
  ],
  "status": "available"
}