Disconnect

unfollow functionality is an integral part of the user experience, designed to offer flexibility and ease in managing user connections. Like the follow API, the unfollow mechanism harnesses the power of typed data, providing a clearer picture to users of the data they're authenticating.

It follows the similar typed data structure as you can find from follow/referral endpoint.

By using the typed data approach, you'll be working with the withSig methods. These can be called by you with your signature, or by any relay with your signature, by querying via unfollow , you can enable gasless transactions.

API Details

Get follow typed data

Query

mutation CreateConnectProfileTypedData($request: DisconnectProfileTypedDataRequest!) {
  createDisconnectProfileTypedData(request: $request) {
    ... on CreateDisconnectProfileBroadcastItemResult {
      id
      expiresAt
      typedData {
        types {
          DisconnectProfileWithSig {
            name
            type
          }
        }
        domain {
          name
          chainId
          version
          verifyingContract
        }
        value {
          disconnectorProfileId
          connectType
          idsOfProfilesToDisconnect
          nonce
          deadline
        }
      }
    }
    ... on AppRelayError {
      error
    }
  }
}

You can then make a unfollow request via gasless mode.

Query

mutation DisconnectProfile($request: DisconnectProfileRequest!) {
  disconnectProfile(request: $request) {
    ... on AppRelayerResult {
      txHash
      profileId
    }
    ... on AppRelayError {
      error
    }
  }
}