Getting started
Cookies and CORS
Cookie and CORS requirements for the session to work across origins.
1 min read
The web SDK session depends on a cookie set by the platform and a CORS configuration that accepts credentials.
The session cookie
The cookie is set by the platform with SameSite=None; Secure. That is why your
page must be served over HTTPS.
Sending credentials
SDK calls to the platform API use credentials: "include".
CORS
The platform responds with Access-Control-Allow-Credentials: true for allowed
origins. Your origin must be among them.
File upload
Sending the file to the signed address does not go through this credentials configuration.
Support
Implementation support
Official channels for questions during integration.
Technical support email
Response within 1 business day
Send implementation questions with the context of your current step.
Send emailResponse according to the support queue
Direct assistance for quick integration questions.
Support assistant
Immediate response
i6 documentation and implementation assistant.