SDK versions

Staying current with SDK versions helps developers take advantage of the latest capabilities and enhancements offered.

URL
Version
Integrity
Changes

v2.3

sha256-D0P+mQ7N6E0tbReEGYNTjoGqRmWUX87oCLd8PNvs5vg=

Content encryption, JWT authentication, enhanced security. 100% Backward Compatible

v2.2

sha256-IzmJZo/gWd+To2rEV/ZC9+fXZZgHfw5E0jZECyq9ipY=

Added support for Google Fonts ('Lato', 'Montserrat', 'Open Sans', 'Oswald', 'Poppins', 'Roboto', 'Raleway', 'Slabo 13px', 'Slabo 27px', 'PT Sans', 'Inter') in the font-family CSS

v2.1

sha256-FbadlNL2dab5uMHBUpFv+jEKsUSg3Cmi0dYvVWQIuZs=

Added support for tags parameter in the initialization function.

v2.0

sha256-qtSTst/JgM5bN+4ZILzXN/DEgAhg2jDYgH5pF9YqeNY=

Added separate date validation events.

v1.0

sha256-5VzwvLiVo4k8snm84TZShTmTWzXBbCM8NyNMXdkx8fw=

Original version

Implementation Recommendations

For New Implementations

Use SDK 2.3 with these options:

Standard Security (Quick Start)

<script src="https://cdn.firstoken.co/captures/js/2.3/sdk.js"></script>
<script>
const FT = window.FTCaptures.init("your-route-id", "production", callback);
</script>
<script src="https://cdn.firstoken.co/captures/js/2.3/sdk.js"></script>
<script>
const FT = window.FTCaptures.init("your-route-id", "production", callback, tags, jwtToken);
</script>

Integrity Verification

Always use integrity hashes in production:

<script 
    src="https://cdn.firstoken.co/captures/js/2.3/sdk.js"
    integrity="sha256-D0P+mQ7N6E0tbReEGYNTjoGqRmWUX87oCLd8PNvs5vg="
    crossorigin="anonymous">
</script>

Version Migration Guides

Migrating from 2.2 to 2.3

  1. Update CDN URL

    <!-- Before -->
    <script src="https://cdn.firstoken.co/captures/js/2.2/sdk.js"></script>
    
    <!-- After -->
    <script src="https://cdn.firstoken.co/captures/js/2.3/sdk.js"></script>
  2. Test functionality - All existing features continue to work

  3. Optional: Implement JWT for enhanced security

  4. Optional: If you need to encrypt the payload you sent to us, please contact the support team to configure this feature in the inbound route you are using.

Resources

Last updated

Was this helpful?