PUT
/
gates
/
{gateId}
/
enable
curl --request PUT \
  --url https://app.dynamicauth.com/api/v0/gates/{gateId}/enable \
  --header 'Authorization: Bearer <token>'
{
  "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"
}

Authorizations

Authorization
string
headerrequired

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

gateId
string
required

ID of the gate

Response

200 - application/json
id
string
required

ID of the gate

name
string
required

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

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.

enabledAt
string | null

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

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.

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