Skip to main content
POST
Unfollow an asset

Overview

Stop the emails for an asset you follow. It undoes Follow Asset, and a follow made with the Follow button in the app can be undone here too. Unfollowing is never refused because of the follow limit — it is how you get back under it. Unfollowing an asset you do not follow is not an error. Like following, it needs a user-scoped API key or a signed-in session.

Quick Start

Authentication

Include your user-scoped API key in the X-API-KEY header:

Example Request

Request Body

Response

The same shape as Follow Asset, with following set to false.

Authorizations

X-API-KEY
string
header
required

Your API key. This is required by most endpoints to access our API programatically. Reach out to us at support@chainpatrol.io to get an API key for your use.

Body

application/json

Unfollow an asset

Stops the status emails for this asset. Never refused for capacity, and unfollowing an asset you do not follow is not an error.

slug
string

Organization slug. Optional when your API key is scoped to one organization. Required when your credentials can reach more than one.

content
string

Asset content: a URL, domain, wallet address, social profile, etc.

Minimum string length: 1
assetId
integer

ChainPatrol asset ID

Required range: x > 0

Response

Successful response

assetId
integer
required

The asset that was followed or unfollowed

following
boolean
required

Whether this person now follows the asset

followCount
integer
required

How many assets this person follows in this organization

limit
integer
required

The most assets one person may follow

warnThreshold
integer
required

The count from which warning is set

canFollowMore
boolean
required

False once followCount reaches limit; following more is refused

warning
string | null
required

Set from warnThreshold upward, asking the caller to unfollow assets