portalnetwork
  • Portal Network
  • Overview
    • Getting Started
    • Introduction to BNS (Blockchain Name Service)
    • Introduction to MUMEI
    • Introduction to KAIZEN
    • Contact Us
  • FAQ: BNS (Blockchain Name Service)
    • What is the BNS standard?
    • What are the BNS Components?
    • What is subdomain?
    • What is the bidding process?
    • How to get a BNS?
    • What blockchain protocols do you support?
    • How are blockchain domains different from the domain we are using today?
    • How can we know if we registered a domain through name service site and what's next?
    • Does "A New Internet" means forgoing the existing DNS system?
  • FAQ: Portal Network Partners and Ecosystem
    • Bitcoin Cash Name Service
    • Ethereum Name Service
    • Ethereum Classic Name Service
    • Enigma Name Service
    • ICON Name Service
    • NKN Name Service
    • NEM Name Service
    • NEO Name Service
    • Qtum Name Service
    • QuarkChain Name Service
    • Wanchain Name Service
    • TomoChain Name Service
  • How to use MUMEI
    • MUMEI Motivation and Architecture
    • Marketplace
    • Domain Manager
    • Web Builder
    • Browser Extension
    • Showcase
    • BNS Explorer
    • BNS Resolver
    • Mobile Application
  • How to use KAIZEN
    • KAIZEN Motivation and Architecture
    • CLI (Command Line Interface)
    • KAIZEN Management System
    • API
    • Universal Infrastructure
    • Tech Guide
    • Faucet
    • Hackathon
  • How to get your own cryptocurrency
    • ETH at Coinbase
    • ETH at MAX
    • ETC at Binance
    • WAN at Binance
Powered by GitBook
On this page
  • Introduction
  • Authentication
  • Errors

Was this helpful?

  1. How to use KAIZEN

API

PreviousKAIZEN Management SystemNextUniversal Infrastructure

Last updated 6 years ago

Was this helpful?

Introduction

A consolidated API inclusive of all endpoints for protocols and tools within the Portal Network, it is an easy access to the Blockchain networks.

Authentication

Portal Network uses API keys to allow access to the API. Users can register a new Portal Network API key here (coming soon).

Portal Network expects for the API key to be included in all API requests to the server in a header that looks like the following:

Authorization: auth_key

Errors

This error section is stored in a separate file in includes/_errors.md. Slate allows you to optionally separate out your docs into many files...just save them to the includes folder and add them to the top of your index.md's frontmatter. Files are included in the order listed.

The Kittn API uses the following error codes:

Error Code

Meaning

400

Bad Request -- Your request is invalid.

401

Unauthorized -- Your API key is wrong.

403

Forbidden -- The kitten requested is hidden for administrators only.

404

Not Found -- The specified kitten could not be found.

405

Method Not Allowed -- You tried to access a kitten with an invalid method.

406

Not Acceptable -- You requested a format that isn't json.

410

Gone -- The kitten requested has been removed from our servers.

418

I'm a teapot.

429

Too Many Requests -- You're requesting too many kittens! Slow down!

500

Internal Server Error -- We had a problem with our server. Try again later.

503

Service Unavailable -- We're temporarily offline for maintenance. Please try again later.

shell
python