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 Auth API

The auth API from VersusGame — 30 operation(s) for auth.

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

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

This API exposes 35 operations across 30 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.

35 operations 30 paths 22 schemas 1 DELETE9 GET2 PATCH23 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 Auth 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 35

Across 30 paths, the API surfaces 35 operations — 1 DELETE, 9 GET, 2 PATCH, 23 POST. Each is listed below with its method, path, parameters, and response codes.

auth 35
POST
/auth/identify
AuthController_identify body → 200
POST
/auth/login
AuthController_login body → 200
POST
/auth/change_password
AuthController_changePassword 1 param body → 200
POST
/auth/reset_password
AuthController_resetPassword body → 204
POST
/auth/reset_password/set_new
AuthController_resetPasswordSetNew body → 200
POST
/auth/reset_password/verify_token
AuthController_resetPasswordVerifyToken → 204
POST
/auth/confirm_invite
AuthController_confirmInvite body → 200
POST
/auth/verify_email
AuthController_verifyEmail → 200
POST
/auth/signup
AuthController_signup body → 200
POST
/auth/resend_email_verification
AuthController_resendEmailVerification body → 200
POST
/auth/refresh
AuthController_refresh 1 param → 200
POST
/auth/logout
AuthController_logout → 204
POST
/auth/validate_email
AuthController_validateEmail body → 204400409
POST
/auth/sign_tos
AuthController_signTos → 204
PATCH
/auth/payout_email
AuthController_updatePayoutEmail body → 200
POST
/auth/payout_email_verification
AuthController_payoutEmailVerification body → 204
POST
/auth/microsoft_rewards
AuthController_microsoftRewards body → 200
POST
/admin/auth/invite
AdminController_invite body → 204
GET
/admin/auth/users
AdminController_list 3 params → 200
POST
/admin/auth/users/{userId}/set_creator
AdminController_setCreator 1 param body → 204
PATCH
/admin/auth/users/{userId}
AdminController_updateUser 1 param body → 204
POST
/superadmin/auth/role/{userId}
SuperAdminController_addRole 1 param body → 204
DELETE
/superadmin/auth/role/{userId}
SuperAdminController_deleteRole 1 param body → 204
GET
/auth/apple
socialControllerAuthapple → 200
GET
/auth/apple/callback
socialControllerAuthCallbackGetapple → 200
POST
/auth/apple/callback
socialControllerAuthCallbackPostapple → 200
GET
/auth/facebook
socialControllerAuthfacebook → 200
GET
/auth/facebook/callback
socialControllerAuthCallbackGetfacebook → 200
POST
/auth/facebook/callback
socialControllerAuthCallbackPostfacebook → 200
GET
/auth/google
socialControllerAuthgoogle → 200
GET
/auth/google/callback
socialControllerAuthCallbackGetgoogle → 200
POST
/auth/google/callback
socialControllerAuthCallbackPostgoogle → 200
GET
/auth/microsoft
socialControllerAuthmicrosoft → 200
GET
/auth/microsoft/callback
socialControllerAuthCallbackGetmicrosoft → 200
POST
/auth/microsoft/callback
socialControllerAuthCallbackPostmicrosoft → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are UserEntity (20 properties), SignupDto (16 properties), CredentialsEntity (11 properties), IdentifyExternalUser (6 properties). Each schema is shown below with its type and property counts.

UpdateUserDto
object
1 property 1 required
UpdatePayoutEmailEntity
object
1 property 1 required
IdentifyExternalUser
object
6 properties 4 required
ResetPasswordDto
object
2 properties 2 required
ResetPasswordSetNewDto
object
1 property 1 required
ListUsersEntity
object
1 property 1 required
ChangePasswordDto
object
2 properties 2 required
UpdatePayoutEmailDto
object
1 property 1 required
ResendEmailVerificationDto
object
3 properties 3 required
AdminInviteUserDto
object
3 properties 1 required
Language
string
SignupDto
object
16 properties 5 required
CredentialsEntity
object
11 properties 8 required
SigninDto
object
2 properties 2 required
MicrosoftRewardsDto
object
3 properties 2 required
Role
string
PayoutEmailVerificationDto
object
1 property 1 required
SetRoleDto
object
1 property 1 required
UserEntity
object
20 properties 13 required
SetCreatorDto
object
4 properties 4 required
ValidateEmailDto
object
1 property 1 required
ConfirmInviteDto
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

versusgame-auth-api-openapi.yml Raw ↑

Other APIs VersusGame publishes across the network.

VersusGame Achievements API
VersusGame App API
VersusGame Assets 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
VersusGame Games API
Where this information came from

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