Empty "rfo" / Reference Order - the customer order ref - Exchange Stream API

[ApiUser]

I'm seeing empty RFO field from the stream update, can you please explain why the SportsAPINGresponse contains the customer ref but the exchange stream API response "rfo" does not?

[ApiUser]

Place order "SportsAPING/v1.0/placeOrders", .. "customerRef":"708041769200",

API synch response:
result: {"jsonrpc":"2.0","result":{ "customerRef":"708041769200", "status":"SUCCESS" ...

Then the stream unmatched order update (empty rfo):
"uo":[{"id":"398921324729","p":16.5,"s":1,"side":"B", "st atus":"E","pt":"P","ot":"L","pd":1755796554000,"sm ":0,"sr":1,"sl":0,"sc":0,"sv":0,"rac":"","rc": "REG _GGC","rfo":"","rfs":""}]}]}]}

[BetfairDeveloperProgram]

Hi ApiUser,

There are two similarly named fields that can be passed in the placeOrders requests (see details below)

You are passing the customerRef and not customerOrderRef

The rfo field relates specifically to the customerOrderRef.

• rfo / Reference Order - the customer supplied order reference

customerRef	String		Optional parameter allowing the client to pass a unique string (up to 32 chars) that is used to de-dupe mistaken re-submissions. customerRef can contain: upper/lower chars, digits, chars : - . _ + * : ; ~ only. Please note: There is a time window associated with the de-duplication of duplicate submissions which is 60 seconds. NB: This field does not persist into the placeOrders response/Order Stream API and should not be confused with customerOrderRef, which is separate field that can be sent in the PlaceInstruction.

Sent within placeInstruction:

customerOrderRef

String

An optional reference customers can set to identify instructions.. No validation will be done on uniqueness and the string is limited to 32 characters. If an empty string is provided it will be treated as null.

Kind Regards

Neil