POKKT Gratification API

Server-to-server rewarded-video confirmation callback. When a user completes a rewarded video, POKKT issues a GET to a publisher-hosted URL configured in the app settings page, carrying app_id, unique_id, timestamp, points, optional encodedPubParams and network_id, plus a token that is an MD5 hash over app_id, unique_id, timestamp, points and the app secret key. POKKT's own guidance is that the callback confirms a reward rather than granting it — the client-side callback grants it. Documentation last updated June 2017.

API entry from apis.yml

apis.yml Raw ↑
aid: pokkt:gratification-api
name: POKKT Gratification API
description: Server-to-server rewarded-video confirmation callback. When a user completes a rewarded video,
  POKKT issues a GET to a publisher-hosted URL configured in the app settings page, carrying app_id, unique_id,
  timestamp, points, optional encodedPubParams and network_id, plus a token that is an MD5 hash over app_id,
  unique_id, timestamp, points and the app secret key. POKKT's own guidance is that the callback confirms
  a reward rather than granting it — the client-side callback grants it. Documentation last updated June
  2017.
humanURL: https://wiki.pokkt.com/api-guide/gratification-api
baseURL: https://{publisher-callback-host}
x-base-url-note: 'Templated on purpose. This is an outbound callback: the endpoint is hosted by the publisher
  and registered on the app settings page in the POKKT console ("[PUBLISHER LINK URL]" in POKKT''s own
  request format), so POKKT publishes no base host of its own for it.'
tags:
- webhooks
- server-to-server
- rewarded-video
- callbacks
properties:
- type: Documentation
  url: https://wiki.pokkt.com/api-guide/gratification-api
- type: Webhooks
  url: asyncapi/pokkt-webhooks.yml
- type: Authentication
  url: authentication/pokkt-authentication.yml