Affiliate Feed API: missing player markets, current access model, and real-time requirements

[viachaslau-babitski]

We operate the Surebet.com odds scanner and currently consume Cloudbet Feed API endpoints under https://sports-api.cloudbet.com/pub/v2/odds/* using an X-API-Key.

Our affiliate manager advised us to use the Affiliate API rather than the player API. The published documentation says that an Affiliate API Key is used with the same Feed API endpoints, but that responses may be cached by up to one minute, while a Trading API Key provides real-time updates.

We currently receive soccer.anytime_goalscorer and soccer.last_goalscorer. However, additional player markets shown on the Cloudbet website — including hat-tricks, player cards, and period-specific player markets — are missing from our API responses.

Could you please clarify:

1. Does “Affiliate API” mean an Affiliate API Key used with the existing Feed API, or is there a separate Product/Partner API, endpoint set, or specification that we should use?
2. Which credential and access tier is intended for an odds-comparison/scanner service that needs complete pre-match and live odds without a one-minute cache delay? Can Affiliate API access be made real-time?
3. Are the missing player markets unavailable to all API clients during the current rebuild, or are they gated by key type, permissions, account tier, endpoint, or request parameters?
4. Are hat-trick, player-card, and period-specific player markets currently exposed? If yes, what are their exact market keys and endpoints? If not, are they planned, and is there an ETA?
5. What is the current canonical, machine-readable list of supported markets? Is the previously published markets.json gist still authoritative?
6. What are the current rate limits, caching rules, and recommended polling strategy for pre-match and live feeds?
7. Do we need to submit the Product API form, obtain commercial approval, whitelist IPs, or provide any other information to enable the correct access?

We can provide masked request examples, event IDs, timestamps, and the returned market-key list if needed.