FetchFragmentsOptions
Defined in: fragments.ts:104
Properties
Section titled “Properties”apiBase
Section titled “apiBase”apiBase:
string
Defined in: fragments.ts:106
apiBaseProvenance?
Section titled “apiBaseProvenance?”
optionalapiBaseProvenance?:"key"|"explicit"
Defined in: fragments.ts:119
Where apiBase came from. The publishable key is an unsigned address
anyone can hand-encode, so a key-derived apiBase earns content fetches
but NOT the mint POST (which carries the signed token — a real spend
credential — and the declared dims) unless the host is first-party or
loopback (S-2). Defaults to “explicit”: a caller passing apiBase
directly has chosen it themselves.
context?
Section titled “context?”
optionalcontext?:DeclaredContext
Defined in: fragments.ts:107
fetchImpl?
Section titled “fetchImpl?”
optionalfetchImpl?: (input,init?) =>Promise<Response>
Defined in: fragments.ts:121
Test seam; defaults to the platform fetch.
Parameters
Section titled “Parameters”URL | RequestInfo
RequestInit
Returns
Section titled “Returns”Promise<Response>
fields
Section titled “fields”fields:
Record<string,FragmentFieldSpec>
Defined in: fragments.ts:108
mintToken?
Section titled “mintToken?”
optionalmintToken?:MintTokenSource
Defined in: fragments.ts:112
Sent on the mint POST only — never on the GET, which is a shared CDN object and must be byte-identical for every caller. Optional: without it the mint goes unsigned and the server admits it or not.
organizationId
Section titled “organizationId”organizationId:
string
Defined in: fragments.ts:105