How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Gameball Orders API

The Orders API from Gameball — 4 operation(s) for orders.

Gameball Orders API is one of 9 APIs that Gameball publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Order. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.

This API exposes 4 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 4.0.0.

Requests are made against a single base URL, https://api.gameball.co.

4 operations 4 paths 4 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.0.0
Base URL
https://api.gameball.co/api/v4.0
Authentication
API Key, API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 3

Gameball Orders API declares 3 security schemes for authenticating requests. An API key is passed in the header as apikey (apiKey). An API key is passed in the header as secretkey (secretKey). It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 1 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Orders 4
POST
/api/v4.0/integrations/orders
Track Order
trackOrder body → 200
POST
/api/v4.0/integrations/orders/cashback
Calculate Order Cashback
calculateOrderCashback body → 200
POST
/api/v4.0/integrations/orders/reward-preview
Preview Order Rewards
previewOrderRewards 1 param body → 200400401
GET
/api/v4.0/integrations/orders/{orderId}/transactions
Order Transactions
getOrderTransactions 1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are RewardPreviewCampaign (12 properties), OrderRewardPreviewResponse (6 properties), RewardPreviewEventResult (5 properties), RewardPreviewProgress (4 properties). Each schema is shown below with its type and property counts.

RewardPreviewCampaign
object
12 properties
RewardPreviewEventResult
object
5 properties
RewardPreviewProgress
object
Present only for ProgressOnly — accumulative / multi-step campaigns the event advances without completing.
4 properties
OrderRewardPreviewResponse
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gameball-orders-api-openapi.yml Raw ↑

Other APIs Gameball publishes across the network.

Gameball MCP Server
Gameball Batches API
Gameball Customers API
Gameball Events API
Gameball Gameball API
Gameball Integrations API
Gameball Payments API
Gameball Plants API
Where this information came from

This is an independent, third-party profile of Gameball Orders API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.