LikeCoin API

LikeCoin API uses OAuth2.0 flow for API authorization, please refer to Authetication section before you use any API.

Production endpoint: https://api.like.co Development endpoint: https://api.rinkeby.like.co

Please contact team[at]like.co for OAuth client id/secret and scope/redirect_uri whitelist.

Endpoints marks with a padlock requires authorization with

Plain Text

Authorization Bearer {{access_token}}

Please refer to Authetication section below to learn how to obtain access_token for an user.

AUTHORIZATIONBearer Token

Token

Register

POSTCheck Liker ID/email available

https://api.like.co/users/new/check

Check if an LikerID and email is available

Also return possible alternative id if id already exists, please check exmaple requests for reference.

HEADERS

Content-Type

application/json

Bodyraw

{
	"user": "williamchong",
	"email": "williamchong@like.co"
}

POSTRegister user via supported platforms

https://api.like.co/users/new/matters?client_id={{CLIENT_ID}}&client_secret={{CLIENT_SECRET}}

Path Params	Description
platform	target plaform, please refer to supported list above

HEADERS

Content-Type

application/json

PARAMS

client_id

client_secret

Bodyraw

{
	"user": "Liker ID",
	"token": "platform specific token",
	"displayName": "(optional) Name used for display in UI. Default: same as `user`",
	"email": "(optional) email address of user",
	"locale": "(optional) `en`/`zh`(zh-TW)/`cn`(zh-CN)/`de`/`es`/`fr`/`it`/`ja`/`ko`/`pt`/`ru`. Default: en",
	"isEmailEnabled": "(optional) does user want to receive email notifications. Default: true",
	"platformUserId": "(optional) platform specific user ID, unused for now",
	"platformUsername": "(optional) platform specific username, unused for now",
	"platformRefreshToken": "(optional) platform specific refresh token, unused for now"
}

Authetication

LikeCoin API uses OAuth2.0 flow for API authorization, through the following steps.

Users authorize your app through web ui https://like.co/in/oauth. For details and params, please refer to [For client user agent] User oAuth page section below

Users are redirected back to a redirect_uri you own with a code, this code is used to exchange for a user access_token and refresh_token.

Call apis using access_token with proper scope. e.g. APIs in Like->info sections requires read:like.info or write:like.info grants.

Available scopes:

Scope	Description
profile	Basic user public information
email	Access to user's email address

The following scope should be prepended with read: or write:

Scope	Description
(read\|write):like	Access to all like related read/write scope
read:like.button	Access to read user like history and suggestions
write:like.button	Permission to like content for user
read:like.info	Access to read user liked authors, content suggestions, etc

Token life time

Access tokens expire in 1 hour. Refresh tokens do not expire, unless:

Another new refresh token was issued for the same oauth client & user combination

User revoked access

OAuth client revoked the token via API