FormsClient
@ebitex/forms-sdk — the framework-agnostic half: fetching a form definition and validating a
submission against it. Neither imports React, so a server-only consumer never pulls it in.
The rendering components live behind a separate entry point, @ebitex/forms-sdk/react. That
split is deliberate and load-bearing: createFormsClient takes an organization-wide API key and
must only ever run server-side, while the components render in a respondent’s browser and must
never receive one. Expressing the boundary in the import graph makes a mistake visible in review.
Methods
Section titled “Methods”getForm()
Section titled “getForm()”getForm(
externalId):Promise<SdkForm>
Parameters
Section titled “Parameters”externalId
Section titled “externalId”string
Returns
Section titled “Returns”Promise<SdkForm>