Hi all,
Hoping a member of the developer team can clarify whether a Delayed App Key can be
used with the Exchange Stream API, as I'm getting conflicting signals from the docs
vs. the behaviour I'm seeing.
Setup: a personal, non-commercial app (algorithmic strategy research/testing against
my own account). It places NO orders — this is integration testing of a data pipeline
only, so delayed, rounded prices are entirely sufficient.
What works:
- REST / API-NG with my Delayed key is fine: login, listMarketCatalogue, market
metadata / instrument discovery all succeed.
What fails:
- Connecting to the Exchange Stream API (stream-api.betfair.com:443) authenticates
successfully, but every market subscription is then refused with:
statusCode: FAILURE
errorCode: NOT_AUTHORIZED
errorMessage: "AppKey is not configured for service"
- Example (UTC): 2026-07-11, 14:53–15:30, subscribing to market 1.259874964
(GB horse racing WIN). Stream connection IDs: 212-110726145341-9660092 and
105-110726152911-10278056.
- (App Key and account username redacted here — happy to share by PM or via my
support ticket.)
Why I think this should work:
The Exchange Stream API documentation seems to contemplate Delayed-key streaming.
It states the conflation field "will be 180000 if you access the Stream API using a
Delayed App Key or have an account delay in place when using the Live App Key." That
reads as though a Delayed key can connect to the Stream API (at 180s conflation) once
it has been configured for the service - which the "not configured for service"
message suggests mine hasn't been.
I've also seen older threads and GitHub issues with the same error left unresolved,
and one secondhand report that support said "delayed key was not available for stream
api" - which appears to contradict the docs above. Hence the question.
My question:
1. Can a Delayed App Key be enabled/provisioned for the Exchange Stream API? If so,
what's the step to have mine configured?
2. If Delayed keys cannot be enabled for streaming as a matter of policy, could
someone confirm that explicitly, so I can plan for Live App Key activation
instead?
I've raised a support ticket separately (21 Jul) with the full details; glad to
provide the App Key / account there or by PM. A clear yes/no on (2) would be a big
help in deciding whether to proceed with the Live key.
Thanks very much!
Hoping a member of the developer team can clarify whether a Delayed App Key can be
used with the Exchange Stream API, as I'm getting conflicting signals from the docs
vs. the behaviour I'm seeing.
Setup: a personal, non-commercial app (algorithmic strategy research/testing against
my own account). It places NO orders — this is integration testing of a data pipeline
only, so delayed, rounded prices are entirely sufficient.
What works:
- REST / API-NG with my Delayed key is fine: login, listMarketCatalogue, market
metadata / instrument discovery all succeed.
What fails:
- Connecting to the Exchange Stream API (stream-api.betfair.com:443) authenticates
successfully, but every market subscription is then refused with:
statusCode: FAILURE
errorCode: NOT_AUTHORIZED
errorMessage: "AppKey is not configured for service"
- Example (UTC): 2026-07-11, 14:53–15:30, subscribing to market 1.259874964
(GB horse racing WIN). Stream connection IDs: 212-110726145341-9660092 and
105-110726152911-10278056.
- (App Key and account username redacted here — happy to share by PM or via my
support ticket.)
Why I think this should work:
The Exchange Stream API documentation seems to contemplate Delayed-key streaming.
It states the conflation field "will be 180000 if you access the Stream API using a
Delayed App Key or have an account delay in place when using the Live App Key." That
reads as though a Delayed key can connect to the Stream API (at 180s conflation) once
it has been configured for the service - which the "not configured for service"
message suggests mine hasn't been.
I've also seen older threads and GitHub issues with the same error left unresolved,
and one secondhand report that support said "delayed key was not available for stream
api" - which appears to contradict the docs above. Hence the question.
My question:
1. Can a Delayed App Key be enabled/provisioned for the Exchange Stream API? If so,
what's the step to have mine configured?
2. If Delayed keys cannot be enabled for streaming as a matter of policy, could
someone confirm that explicitly, so I can plan for Live App Key activation
instead?
I've raised a support ticket separately (21 Jul) with the full details; glad to
provide the App Key / account there or by PM. A clear yes/no on (2) would be a big
help in deciding whether to proceed with the Live key.
Thanks very much!
Comment