POST
/
environments
/
{environmentId}
/
gates
curl --request POST \
  --url https://app.dynamicauth.com/api/v0/environments/{environmentId}/gates \
  --header 'Content-Type: application/json' \
  --data '{
  "name": "Super User Gate",
  "outcome": "scope",
  "scope": "superuser",
  "rules": [
    {
      "type": "nft",
      "address": {
        "networkId": 1,
        "contractAddress": "0xbF394748301603f18d953C90F0b087CBEC0E1834"
      },
      "filter": {
        "tokenId": "0x01",
        "amount": 123
      }
    }
  ]
}'
{
  "id": "95b11417-f18f-457f-8804-68e361f9164f",
  "name": "Super User Gate",
  "scope": "superuser",
  "enabledAt": "2023-11-07T05:31:56Z",
  "rules": [
    {
      "type": "nft",
      "address": {
        "networkId": 1,
        "contractAddress": "0xbF394748301603f18d953C90F0b087CBEC0E1834"
      },
      "filter": {
        "tokenId": "0x01",
        "amount": 123
      }
    }
  ],
  "outcome": "scope"
}

Path Parameters

​
environmentId
string
required

ID of the environment

Required string length: 36
Example:

"95b11417-f18f-457f-8804-68e361f9164f"

Body

application/json

Request body to create a new gate. The gate will be not enabled by default.

​
name
string
required

Human-readable name of the gate. This should be something helpful to organize gates.

Example:

"Super User Gate"

​
outcome
enum<string>
required
Available options:
scope,
siteAccess,
block
​
rules
object[]
required

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.

Definition for a single rule in a Gate. This will check for the presence of a token or NFT, given the contract address, in the wallet of a user being evaluated. For multi-wallet users, we will check all wallets. If a filter is defined, then we will also check that the filter checks apply to the user

​
scope
string

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.

Example:

"superuser"

Response

201
application/json
Successfully created
​
id
string
required
Required string length: 36
Example:

"95b11417-f18f-457f-8804-68e361f9164f"

​
name
string
required

Human-readable name of the gate. This should be something helpful to organize gates.

Example:

"Super User Gate"

​
rules
object[]
required

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.

Definition for a single rule in a Gate. This will check for the presence of a token or NFT, given the contract address, in the wallet of a user being evaluated. For multi-wallet users, we will check all wallets. If a filter is defined, then we will also check that the filter checks apply to the user

​
outcome
enum<string>
required
Available options:
scope,
siteAccess,
block
​
scope
string

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.

Example:

"superuser"

​
enabledAt
string | null

If the gate is enabled, then this timestamp will be present.

Was this page helpful?