Project & Player Requests
Learn more about Project and Player Requests
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.
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 | ❌ |
AuthPlayer | ✔️️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 | ❌ |
GetPlatform | ✔️️Able to Run | ✔️️Able to Run |
GetPlayer | ✔️️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 | ❌ |
DeletePlayer | ✔️️Able to Run | ❌ |
InvalidateAssetMetadata | ✔️️Able to Run | ❌ |
UnlinkWallet | ✔️️Able to Run | ✔️️Able to Run |
AdvancedSendAsset | ✔️️Able to Run | ✔️️Able to Run |
CompleteTrade | ✔️️Able to Run | ❌ |
CreateAsset | ✔️️Able to Run | ❌ |
CreateTrade | ✔️️Able to Run | ❌ |
DecreaseMaxMeltFee | ✔️️Able to Run | ❌ |
DecreaseMaxTransferFee | ✔️️Able to Run | ❌ |
MeltAsset | ✔️️Able to Run | ✔️️Able to Run |
Message | ✔️️Able to Run | ✔️️Able to Run |
MintAsset | ✔️️Able to Run | ❌ |
ReleaseReserve | ✔️️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 | ❌ |
SetMeltFee | ✔️️Able to Run | ❌ |
SetTransferFee | ✔️️Able to Run | ❌ |
SetTransferable | ✔️️Able to Run | ❌ |
SetWhitelisted | ✔️️Able to Run | ❌ |
UpdateName | ✔️️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.