@doola/js changelog. Changes to the Partner API endpoints the SDK uses are in the Partner API changelog.
No action needed. You no longer send doola the domains that host the SDK. Signing renders inside the SDK on any HTTPS page, and with test keys on any page,
localhost included. See Signatures.doola answers a session with 409 for three reasons, and
onAuthError now names each one: email_in_use, the new external_id_conflict and the new customer_revoked. The founder sees a message for each, and never the email message unless the email is the cause.Forward doola’s error code to get them. @doola/js/server answers a 409 with { code }, and fetchAccessToken rejects with it; see Embed the SDK and Errors. A route that sends only the status keeps getting email_in_use for a first 409. On a renewal, a 409 with E_EMAIL_IN_USE or with no code is renewal_failed. If you switch on error.type exhaustively, add the two new cases.The Embedded SDK has its own section in these docs: a quickstart, the payment guide, testing and a go-live checklist, and references for the client, the server helpers and errors.The Partner API reference now lists every error Confirm payment and Create a customer session return, and the optional Get your publishable key endpoint.
@doola/js/serveraddscreateSessionHandlerandcreateCustomerSession, which build your session route. See Create sessions.- Trusted Types. Sites that enforce Trusted Types can allow the
doola-jspolicy. See Security and data.
CommonJS projects using
node16 or nodenext module resolution get the right type definitions.