Tebex API

Games & Comics / X-Mashape-Key Intermediate HTTPS
Check official documentation

Overview

Tebex is a monetisation platform for game servers, and its API lets you retrieve information about packages, purchases, and player data for your game store. It requires a special API key obtained from your Tebex account dashboard. Developers use it to build custom storefronts or automate in-game reward delivery.

Beginner Tip

You must have an active Tebex store to generate an API key. Use the secret key from your store settings, not the public webstore identifier.

Available Data

Tebex data via REST API
Requires X-Mashape-Key authentication

Example Response

JSON Response
{
  "id": 1,
  "name": "Tebex",
  "data": "Tebex API for information about game purchases",
  "source": "Tebex"
}

Field Reference

id Unique numeric identifier for the store or package.
name Display name of your Tebex game store.
currency ISO 4217 currency code used by your store, e.g. USD or GBP.
packages List of purchasable packages available on the store.
online Whether the game server associated with the store is currently online.

Implementation Example

Request
const url = "https://docs.tebex.io/plugin/";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "X-API-Key": "YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

403 Forbidden Invalid or missing X-Tebex-Secret header.
Copy the exact secret key from your Tebex store dashboard under API settings.
404 Not Found The package or player ID you requested does not exist on your store.
List all packages first via /packages endpoint and use IDs from the response.
422 Unprocessable Entity A required request body field is missing or malformed.
Refer to the Tebex plugin documentation for the required JSON body fields for each endpoint.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth X-Mashape-Key
HTTPS REQUIRED
CORS NO
Category Games & Comics
Difficulty Intermediate
Verified: 2026-04-04

Related Tags

Similar APIs

View All →