Denne oversættelse er maskinoversat og afventer gennemgang.Skift til engelsk
Mørk
Log indAnmod om en gennemgang
På denne side
Udvikleroversigt

Integration Flow

The developer overview is the short evaluator path and current support matrix. This guide expands the ownership checkpoints without creating a second set of snippets.

1. Customer client

Load the verified public browser collector for the provisioned origin. The client reports either a collection result or an unavailable state. When a result contains a device identifier, pass only that identifier to your backend with the customer action it will inform.

JavaScript disabled, blocked collection, reduced capability, tenant policy, and consent state can change what evidence is available. The customer journey must remain usable.

2. Noxtica processing

Noxtica processes evidence admitted by the evaluated browser and tenant configuration. A completed browser result can expose less than the authenticated server record. Do not infer low risk from an absent browser score.

3. Customer server

Keep the credential secret and perform the authenticated v1 device lookup. Preserve received, missing, invalid, rate-limited, and unavailable states. Apply a deadline rather than waiting indefinitely on a customer-facing operation.

4. Customer policy

Your application combines the lookup with context it already owns. It chooses whether to continue, observe, request additional verification, review, or deny. Noxtica does not autonomously make that final customer decision.

5. Investigation and measurement

Confirm collection and lookup behavior, calculate proposed actions in observation mode, label outcomes from your own systems, review false-positive cost, and only then promote a bounded policy. Keep an owner and rollback path.

Evaluation checkpoints

  1. Provision the exact origin and public Site Key.
  2. Observe collection and unavailable behavior.
  3. Pass the returned identifier to the customer backend.
  4. Perform an authenticated read with a server-held credential.
  5. Exercise every result state in the maintained fixture.
  6. Evaluate policy in observation mode before enforcement.

Continue with Browser Runtime or Backend Integration.