Project & Player Requests

Project Schema
The project schema has all of its queries and mutations scoped to a singular project. This means that a project access token has unfettered control over everything to do with itself, this includes player authentication.
A project can do any task related to itself or its players (eg. the project can query any player's wallet). This can be seen as the project administrator.
Player Schema
The player schema, on the other hand, is restricted to a singular player for a given project. This means that they can only query/mutate data that relates directly to themselves. This means that you cannot, for example, fetch the wallet address of another player or retrieve a list of players for the project.
A player can only do tasks related to itself (eg. Bob can only query their own wallet, cannot query Alice's wallet) and cannot create assets.
Project x Player Schemas Table.
The following table shows the differences between Project and Player schema permissions while running Queries and Mutations on GraphQL Playground.
Queries
Mutations
Query
Project
Player
GetProject
✔️️Able to Run
✔️️Able to Run
AuthProject
✔️️Able to Run
​❌
Not able to Run
AuthPlayer
✔️️Able to Run
​❌
Not able to Run
GetBalances
✔️️Able to Run
✔️️Able to Run
GetGasPrice
✔️️Able to Run
✔️️Able to Run
GetWallet
✔️️Able to Run
✔️️Able to Run
GetWallets
✔️️Able to Run
​❌
Not able to Run
GetPlatform
✔️️Able to Run
✔️️Able to Run
GetPlayer
✔️️Able to Run
​❌
Not able to Run
GetAsset
✔️️Able to Run
✔️️Able to Run
GetAssets
✔️️Able to Run
✔️️Able to Run
GetTransaction
✔️️Able to Run
✔️️Able to Run
GetTransactions
✔️️Able to Run
✔️️Able to Run
Mutation
Project
Player
CancelTransaction
✔️️Able to Run
✔️️Able to Run
CreatePlayer
✔️️Able to Run
​❌
Not able to Run
DeletePlayer
✔️️Able to Run
​❌
Not able to Run
InvalidateAssetMetadata
✔️️Able to Run
​❌
Not able to Run
UnlinkWallet
✔️️Able to Run
✔️️Able to Run
AdvancedSendAsset
✔️️Able to Run
✔️️Able to Run
CompleteTrade
✔️️Able to Run
​❌
Not able to Run
CreateAsset
✔️️Able to Run
​❌
Not able to Run
CreateTrade
✔️️Able to Run
​❌
Not able to Run
DecreaseMaxMeltFee
✔️️Able to Run
​❌
Not able to Run
DecreaseMaxTransferFee
✔️️Able to Run
​❌
Not able to Run
MeltAsset
✔️️Able to Run
✔️️Able to Run
Message
✔️️Able to Run
✔️️Able to Run
MintAsset
✔️️Able to Run
​❌
Not able to Run
ReleaseReserve
✔️️Able to Run
​❌
Not able to Run
SendEnj
✔️️Able to Run
✔️️Able to Run
SendAsset
✔️️Able to Run
✔️️Able to Run
SetApprovalForAll
✔️️Able to Run
✔️️Able to Run
SetUri
✔️️Able to Run
​❌
Not able to Run
SetMeltFee
✔️️Able to Run
​❌
Not able to Run
SetTransferFee
✔️️Able to Run
​❌
Not able to Run
SetTransferable
✔️️Able to Run
​❌
Not able to Run
SetWhitelisted
✔️️Able to Run
​❌
Not able to Run
UpdateName
✔️️Able to Run
​❌
Not able to Run
ApproveEnj
✔️️Able to Run
✔️️Able to Run
ApproveMaxEnj
✔️️Able to Run
✔️️Able to Run
ResetEnjApproval
✔️️Able to Run
✔️️Able to Run
BridgeAsset
✔️️Able to Run
✔️️Able to Run
BridgeAssets
✔️️Able to Run
✔️️Able to Run
BridgeClaimAsset
✔️️Able to Run
✔️️Able to Run
Project and Player schemas are part of the V.2 Enjin API schemas, which can be enabled by accessing the Projects settings on your project page.

Authentication

Next - Getting Started with the Enjin Platform API

Quick Start-up Guide to use Goërli

Last modified 4mo ago

Export as PDF

Copy link

On this page

Project Schema

Player Schema