API Documentation
/api
Authentication
/api#authentication
Welcome to the Misaka.io API documentation.
/api
API tokens can be created in the API token page.
/api#authentication
This documentation provides comprehensive information about the Misaka.io REST API, including authentication, endpoints, request/response formats, and examples to help you integrate with our platform.
/api
The complete OpenAPI 3.1 specification is available in JSON format for use with API clients, code generators, and documentation tools.
/api#getting-started
This is the v3alpha API documentation, which is still under active development. Breaking changes may occur in future releases. We do not recommend using this API in production environments.
/api
API
/services/dns/api
Our API documentation can be found here.
/services/dns/api
BYOIP / Public BGP Service
/network/byoip
BGP Sessions
/network/byoip#bgp-sessions
We only permit route objects from authoritative IRRs (ARIN, RIPE, APNIC, AFRINIC, LACNIC).
/network/byoip#restrictions
For customers preferring not managing BGP sessions by themselves, we can announce customer prefixes under AS47553 or customer's ASN.
/network/byoip#managed-bgp-announcements
The set-up fee is $75 per ASN per account, and it's non-refundable. Once the service is activated, you can create BGP sessions from VM's networking tab.
/network/byoip#bgp-sessions
Privacy Policy
/legal/privacy
Signature API, Inc.
/legal/privacy#list-of-data-sub-processors
BGP / BYOIP
/services/mc2/bgp/overview
One VM can only have one BGP session pair (IPv4 + IPv6 under same ASN).<br /> If you need to have multiple BGP sessions, you can create multiple VMs and configure them separately.
/services/mc2/bgp/overview#configuration
Once the BGP feature is enabled for your account, you can configure BGP sessions in the Networking tab of each VM.
/services/mc2/bgp/overview#configuration
Communities
/network/communities
In Berlin, by default we add the following communities to NL-IX Route Server sessions:
/network/communities#ber02-berlin
Peering
/network/peering
Peers must establish BGP sessions with all neighbors and enable multiple routing when multiple connections exist.
/network/peering#ix-peering
Peers should not point a gateway of last resort or default route directed towards our session. We may blackhole your MAC address without prior notice if you do so.
/network/peering#general
Network
/network
Note: AS57695 is being phased out and we encourage you to move peering sessions to AS917 instead.
/network#misakaio-asns
Terms of Service
/legal/tos
Including but not limited to access to other computers, networks, devices, and accounts without authorization, transmission, distribution or storage of information, data or material that in violation of laws and regulations of the United States and your country, in violation of copyright, trademark, trade secret, or other intellectual property rights.
/legal/tos#illegal-usages
Changelog
/services/mc2/changelog
Simultaneously, we are updating our network core to the Arista 7280R series routers. Such a move is projected to bolster the stability and reliability of our services. After that, we'll be equipped to offer 100Gbps ports across all our locations. Furthermore, users will have the convenience of overriding the routing policy either via our API or the console.
/services/mc2/changelog#september-2023