ReadonlybodyThe nav_chain field of a signed body or query: the chain when the
platform is observed to send it there and a chain is recorded, undefined
otherwise. Android sends it; iOS has no observation of nav_chain in any
request body, so it omits the field rather than porting Android's shape.
Readonlyclientx-ig-client-endpoint; undefined while the platform renders none.
Readonlycontainercontainer_module of the screen in front in the platform's own spelling;
undefined when the platform has no observed spelling for the screen, so
the field is omitted (never an Android spelling on iOS, never an invented
default for a screen no recording names).
ReadonlycurrentEndpoint module of the screen in front: the module part of its
x-ig-client-endpoint (the catalog's endpointModule when it names one,
else its chain module). Request bodies that name the screen they were sent
from as a module (from_module) read this, never a caller literal.
undefined before the first screen.
ReadonlycurrentChain module of the screen in front in the platform's spelling: the value
get_account_family reports as request_source. undefined before the
first screen or when the platform has no spelling for it.
ReadonlycurrentWhen the screen in front last came to front, for a navigation-derived request field; undefined before the first screen.
ReadonlynavThe header rendering (x-ig-nav-chain); undefined while the platform
renders none (Android: nothing recorded yet; iOS: a screen no recording
names). iOS also has a sentinel for "no screen yet" (not_init), which is
this header's value and never a body's.
What the navigation state looks like on the wire, in the platform's spelling. One value feeds every place a request names the navigation: the
x-ig-nav-chainheader and thenav_chainfield of a body, thex-ig-client-endpointheader, and thecontainer_modulefield — so they can never disagree.