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.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/gratification-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

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:
- Webhook
- Server-to-Server
- Rewarded Video
- Callbacks
tags_raw:
- 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