Skip to main content

Getting Started

Welcome to the Intraverse Backend API documentation. This comprehensive guide will help you understand and integrate with our gaming platform's backend services.

What is Intraverse?

Intraverse is a comprehensive gaming platform that provides:

  • Tournament Management: Create and manage competitive gaming tournaments
  • NFT Integration: Seamless NFT drops and wallet integration
  • Game Point System: Track and manage player points across games
  • Authentication: Secure authentication with magic links
  • Drop System: NFT and token distribution system

Key Features

  • RESTful API: Clean, consistent API design
  • Real-time Updates: WebSocket support for live updates
  • Multi-chain Support: Ethereum, Polygon, and other blockchain networks
  • Scalable Architecture: Built for high-performance gaming applications

This guide will help you get started with the Intraverse Backend API integration.

Prerequisites

Before you begin, make sure you have:

  • A valid API key from Intraverse
  • Basic knowledge of REST APIs
  • Understanding of blockchain concepts (for NFT features)

Quick Start

1. Get Your API Key

Contact our team to get your API key and access credentials.

2. Set Up Your Environment

# Set your API key as an environment variable
export INTRAVERSE_API_KEY="your-api-key-here"
export INTRAVERSE_BASE_URL="https://api.intraverse.io/"

3. Choose authentication path

There are 2 methods you can use our apis

  • With Integrated Authentication (recommended)
  • Without Authentication

Integrated Authentication

  1. Follow this guide to setup your users for authentication Authentication
  2. Authenticated your users by redirecting them to the login page
  3. use the returned token Bearer token authentication. Include your API key in the Authorization header:
Authorization: Bearer user-api-token

Without Authentication

You have to setup the wallet connection, connect users on your side, and when you want to interact with the webservice, like setting the score, you can send the walletAddress as a parameter to our service.

This might take a bit to setup and handle the edge cases, hence we recommend using the first approach.

Base URL

All API requests should be made to:

https://api.intraverse.io/

Error Handling

The API returns standard HTTP status codes:

  • 200: Success
  • 400: Bad Request
  • 401: Unauthorized
  • 403: Forbidden
  • 404: Not Found
  • 429: Rate Limited
  • 500: Internal Server Error

Next Steps

Support

If you need help or have questions: