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

VersusGame Payments API

The payments API from VersusGame — 10 operation(s) for payments.

VersusGame Payments API is one of 32 APIs that VersusGame publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 10 operations across 10 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against the base URL https://api.versusgame.com.

10 operations 10 paths 22 schemas 4 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.versusgame.com
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

VersusGame Payments API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (access-token). An API key is passed in the header as x-api-key (x-api-key).

  • access-token — Enter the bearer token below (do not include 'Bearer')
  • x-api-key — API Key For External calls

Paths & Operations 10

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

payments 10
POST
/v1/payments/payout/business
PaymentsController_makeBusinessPayout body → 201
POST
/v1/payments/payout/gcow
PaymentsController_gcowPayout 1 param body → 200
GET
/v1/payments/payout/gcow/{id}
PaymentsController_gcowPayoutById 1 param → 200
POST
/v1/payments/callback/gcow
PaymentsController_gcowCallback body → 200
POST
/v1/payments/stripe/create
PaymentsController_create 1 param body → 201
GET
/v1/payments/stripe/{id}
PaymentsController_byId 1 param → 200
POST
/v1/payments/callback/stripe
PaymentsController_stripeCallback 1 param → 200
POST
/v1/payments/buy-ticket-bundle-coin
PaymentsController_buyTicketsWithCoin body → 204
GET
/v1/admin/payout/business
BusinessAdminController_listBusiness 6 params → 200
GET
/v1/admin/payout/business/{id}
BusinessAdminController_businessById 1 param → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are WalletResponse (21 properties), ProductEntity (10 properties), StripeEntity (9 properties), Creator (8 properties). Each schema is shown below with its type and property counts.

GcowPayout
object
8 properties 8 required
BuyTicketsDto
object
1 property 1 required
ExpandedBusiness
object
7 properties 7 required
WalletLeague
object
2 properties 2 required
CreateStripePaymentDto
object
1 property 1 required
DailySetCount
object
4 properties 4 required
BusinessExpand
string
StripeEntity
object
9 properties 9 required
SearchFindBusinessDto
object
2 properties
SortFindBusinessDto
object
2 properties
ProductEntity
object
10 properties 10 required
PaymentStatus
string
BusinessPayoutV2Dto
object
1 property 1 required
Language
string
ListExpandedBusinessEntity
object
2 properties 2 required
WalletResponse
object
21 properties 20 required
Creator
object
8 properties 8 required
SortMode
string
Business
object
5 properties 5 required
CallbackDto
object
8 properties 8 required
RewardLinkTypes
string
GcowPayoutDto
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

versusgame-payments-api-openapi.yml Raw ↑

Other APIs VersusGame publishes across the network.

VersusGame Achievements API
VersusGame App API
VersusGame Assets API
VersusGame Auth API
VersusGame Autogame API
VersusGame Autogame/article/v2 API
VersusGame Buddy List API
VersusGame Categories API
VersusGame Creators API
VersusGame Custom URLS API
VersusGame Cuts API
VersusGame Gameplays API
Where this information came from

This is an independent, third-party profile of VersusGame Payments 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.