- Announcements
- System Status
- Introduction
- allowlists
- analytics
- chainalysis
- chains
- custom fields
- environments
- events
- exports
- externaljwt
- gates
- members
- organizations
- origins
- projects
- invites
- sdk views
- settings
- tokens
- sessions
- users
- wallets
- webhooks
- Schemas
Rest API
Get the gates for an environment
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
ID of the environment
Path Parameters
ID of the environment
Response
ID of the environment
Human-readable name of the gate. This should be something helpful to organize gates.
String for the resulting scope of the gate. If the rules of the gate apply to the user being verified, then this scope will be surfaced in the JWT. If a scope is not provided for the gate, the default behavior of the gate would be to block access to users that the rules do not currently apply to.
If the gate is enabled, then this timestamp will be present.
The rules which will be used to evaluate users being verified. If multiple rules are present in a single gate, then all the rules need to apply for the user to gain the scope defined by the gate.
nft, token Defines one token address connected with network Id on which it's working
Id of the network
Valid blockchain wallet address, must be an alphanumeric string without any special characters
Defines the filter properties used for the gate
Minimum token or NFT amount held by the user. If this amount field is provided, then Dynamic will also check that the user has this minimum amount held by the user of the NFT or Token
scope, siteAccess, block Was this page helpful?