React to an entry
POST /v1/changelog/widget/entries/{entry_id}/reactions
One reaction per person per entry: a new one replaces the old. The person is the verified user_id, else client_id; one of them is required. The reaction must be in the project’s reaction set. Stored: the entry, u:<user id> or c:<client id>, the reaction and when.
Auth: Publishable key from the browser, or a secret key. To act as a signed-in person send user_id and user_hash = HMAC-SHA256(signing secret, user_id) as lowercase hex (the same signing secret as the notification bell; header X-Nordva-User-Hash, or user_hash in the query or body). A user_id with a missing or wrong hash answers USER_HASH_INVALID (403); it is never quietly treated as anonymous. A secret key may name any user_id without a hash, to preview what that person sees. client_id is the widget’s random id for one browser (16 to 64 letters, digits, - or _) and is used only for reactions.
Rate limits: browser calls count against 120 requests a minute per IP address, not the key’s budget.
CORS: Access-Control-Allow-Origin: *.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Request Body required
Section titled “Request Body required ”object
Responses
Section titled “ Responses ”Counts after the change
object
object
Count per reaction in the project’s reaction set, in its order.
object
Example
{ "like": 24, "celebrate": 9, "dislike": 1}object
Error envelope. See error.code for the discriminator.
object
object
object
Error envelope. See error.code for the discriminator.
object
object
object
Error envelope. See error.code for the discriminator.
object
object
object
Error envelope. See error.code for the discriminator.