WIP: Migrate SDK to APIv4 #125
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR upgrades the Server SDK to the Server API v4. It removes Server APIv3 specific behavior and aligns the SDK with the new events format shared by Server API and Webhooks.
INTER-1491
❓ Why?
data/products/resultnesting), switches to Bearer auth, unifies Webhooks & Server APIeventformats, and deprecates/visitorsin favor of/v4/events.⚙️ What Changed?
FingerprintPro.ServerSdktoFingerprint.ServerSdk.usingdirectives and type references must change fromFingerprintPro.ServerSdktoFingerprint.ServerSdk.update them to the new names.
📦 Migration Guide (SDK Consumers)
using FingerprintPro.ServerSdk;->using Fingerprint.ServerSdk;.Model.*) to thenew root namespace.
image/tag and use the updated
docker-compose.ymlfile.pipeline/script, update the paths to
Fingerprint.ServerSdk/.