Skip to main content

JS Integration Endpoint

GET 
/:serviceKey/:transactionId/JS

Generates a unique session identifier (uniqid) and returns the MCP Shield JavaScript snippet that must be injected into the client page.

Behaviour:

  • The JS snippet collects device, browser and contextual data from the client.
  • The collected data is associated with the uniqid and transactionId.
  • Subsequent calls to the Block API refer to the same session context via this uniqid.

The uniqid returned by this endpoint is required for:

  • The Block API /appblock.
  • The Verification API /confirm.

JS Integration sequence (verbal description):

  • The Client backend calls the JS Integration endpoint with serviceKey and transactionId, plus query parameters such as lpu, user_ip and head.
  • The Shield API responds with a uniqid and a JS source string.
  • The backend embeds the returned JS into the HTML that is sent to the client browser.
  • The browser executes the JS, sending telemetry and fingerprinting data to Shield in the background, linked to the uniqid.

Request​

Responses​

Successful response containing uniqid and the Shield script source.

Response Headers
    X-ResponseTime

    Total time taken to process the request, generated by the MCP Shield backend.

    Server

    Server identifier returned by the API.