Pokkt · Authentication Profile
Pokkt Authentication
Authentication
Pokkt secures its APIs with apiKey, custom-hash-signature, and undocumented-header across 4 declared security schemes, as derived from its OpenAPI definitions.
CompanyAdvertisingMonetizationMobileVideo AdvertisingAdTechRemarketingOpenRTBProgrammatic AdvertisingRewarded VideoMobile SDKAd ServingConnected TVSupply Side PlatformDSP
Methods: apiKey, custom-hash-signature, undocumented-header
Schemes: 4
OAuth flows:
API key in: query, path
Security Schemes
appId apiKey
· in: query (appId)
appId-path-segment apiKey
· in: path ()
gratification-callback-token custom-hash-signature
· in: query (token)
console-authorization-header undocumented-header
· in: header (Authorization)
Source
Authentication Profile
generated: '2026-08-12'
method: searched
source: >-
https://wiki.pokkt.com/api-guide/interstitial-api.md,
https://wiki.pokkt.com/api-guide/gratification-api.md,
https://wiki.pokkt.com/dsp-integration-guide/pokkt-dsp.md,
live probe of https://api.pokkt.com/graphql
docs: https://wiki.pokkt.com/api-guide
note: >-
Derived by hand from POKKT's own documentation and one live unauthenticated probe, because
there is no OpenAPI to mine securitySchemes from. POKKT has no OAuth, no OIDC, no scopes and no
key-rotation story; identity on the public ad surface is a plain appId in the query string,
and the only cryptographic material anywhere is a shared app secret key used to MD5-sign the
rewarded-video callback back to the publisher.
summary:
types: [apiKey, custom-hash-signature, undocumented-header]
api_key_in: [query, path]
oauth2_flows: []
openid_connect: false
mutual_tls: false
bearer_tokens: false
schemes:
- name: appId
type: apiKey
in: query
parameter: appId
applies_to: [ad-server-api, vast-video-api, mobile-web-video-api]
issued_by: POKKT dashboard ("Your unique App ID (available in POKKT dashboard)")
secret: false
note: >-
The appId is the caller's whole identity on the ad-serving surface. It is mandatory, it
travels in the URL, and there is no accompanying secret, signature or token on the request.
source: https://wiki.pokkt.com/api-guide/interstitial-api.md
- name: appId-path-segment
type: apiKey
in: path
parameter: '<yourappid>'
applies_to: [dsp-openrtb]
endpoint_pattern: 'https://vdo.pokkt.com/api/rtb/<yourappid>'
issued_by: 'account manager ("Please reach out to your account manager for App ID details")'
secret: false
source: https://wiki.pokkt.com/dsp-integration-guide/pokkt-dsp.md
- name: gratification-callback-token
type: custom-hash-signature
in: query
parameter: token
algorithm: md5
signed_input: app_id + unique_id + timestamp + points + app secret key
secret_location: app settings page in the POKKT console
direction: POKKT -> publisher
applies_to: [gratification-api]
note: >-
The only shared secret POKKT documents. It authenticates POKKT's outbound reward callback to
the publisher's endpoint, not the publisher's calls to POKKT. MD5 over concatenated fields is
not an HMAC; there is no signature header, no key id, no algorithm agility and no documented
rotation procedure.
source: https://wiki.pokkt.com/api-guide/gratification-api.md
- name: console-authorization-header
type: undocumented-header
in: header
parameter: Authorization
applies_to: [console-graphql]
method: probed
evidence: >-
An anonymous POST of the introspection query to https://api.pokkt.com/graphql on 2026-08-12
returned {"errors":[{"extensions":{"payload":{"status":401,"message":"Invalid authorization
header format"}}}]}. The header is therefore required; its format, issuance and lifetime are
not published anywhere.
source: https://api.pokkt.com/graphql
publisher_side_credentials:
app_secret_key:
where: app settings page in the POKKT console
used_for: MD5 token on the rewarded-video server-side callback
rotation_documented: false
callback_url:
where: app settings page in the POKKT console
note: 'Documentation calls it a "secure rewarded server-side callback" but does not require HTTPS in the published request format.'
not_found:
- {mechanism: OAuth 2.0, probed: '/.well-known/oauth-authorization-server + /.well-known/oauth-protected-resource on 5 hosts, developer wiki', result: absent}
- {mechanism: OpenID Connect, probed: /.well-known/openid-configuration on 5 hosts, result: absent}
- {mechanism: scopes / permissions model, probed: developer wiki, result: absent — scopes/ deliberately not written}
- {mechanism: mutual TLS, probed: developer wiki, result: absent}
- {mechanism: key rotation or revocation policy, probed: developer wiki, result: absent}
- {mechanism: public self-service key issuance, probed: pokkt.com, result: 'absent — pokkt.com root is the console login SPA; access is account-manager mediated'}
Work with this as data
Every security artifact 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 security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.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.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/pokkt-authentication"
All security posture
curl "https://apis.io/api/v1/security?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.