Skip to main content
Before you start: Read the general Akamai guideThis document only covers deploying the Fingerprint Akamai proxy integration using the Akamai Property Manager API (PAPI). It assumes you have already read the general Akamai guide and completed the following steps:
  • Step 1: You have issued a proxy secret in the Fingerprint Dashboard (FPJS_PROXY_SECRET).
  • Step 2: You have defined a path variable for the integration (FPJS_INTEGRATION_PATH)
If you want to use Terraform instead of PAPI to install the integration, see Deploy Akamai proxy integration using Terraform.
LimitationsThis integration is exclusively supported for customers on the Enterprise Plan. Other customers are encouraged to use Custom subdomain setup or Cloudflare Proxy Integration.

Prerequisites

This deployment guide assumes you already have a working Akamai property and are familiar with the Akamai Control Panel. It uses Postman to make the HTTP requests, but feel free to adjust the instructions to use your preferred HTTP client.

Step 3: Authenticate with EdgeGrid

  1. Follow the Akamai documentation to Create EdgeGrid authentication credentials. You should end up downloading a credentials text file containing the values used below.
  2. Inside Postman, use the values from the credentials file to configure the EdgeGrid authentication for your HTTP requests:
    1. Go to the Authorization tab.
    2. Set the Type to Akamai EdgeGrid.
    3. Set Access Token, Client Token, and Client Secret to the values from the credentials file.
    4. Set the base URL of the request according to the host value from the credentials file, e.g. https://akab-xxxxxxxx.luna.akamaiapis.net.
Note: If your HTTP client does not support EdgeGrid authentication, you can use the same values to manually create the EdgeGrid authentication header. See the EdgeGrid Protocol Specification for more details.

Step 4: Clone the Akamai integration repository

  1. Clone the repository:
  1. Install dependencies using PNPM:

Step 5: Generate Patch Body

Use the build npm command to generate the integration’s property rules for your Akamai property. Use the values from previous steps to configure the command:
Replace variables between double quotes with the values you want to use. For example, "FPJS_INTEGRATION_PATH" should be replaced with the value you set for FPJS_INTEGRATION_PATH in Step 2.
The output will be saved to dist/patch-body/body.json.

Step 6: Deploy using Property Manager API

Use the following sequence of PAPI requests to collect the necessary data and deploy the integration.
  • baseURL is created from the host value from the credentials file, e.g. https://akab-xxxxxxxx.luna.akamaiapis.net.
  • Authenticate all requests using EdgeGrid credentials as described in Step 3.

Step 6.1: Get your Contract ID

Sample Response:
Save the contractId to use in later requests.

Step 6.2: Get your Group ID

Sample Response:
Save the groupId associated with your contractId to use in later requests.

Step 6.3: Get your Property ID

Sample Response:
Find the property you want to deploy the integration to. Save its propertyId and latestVersion to use in later requests. To make changes to your property, you first need to clone one of its versions. To decide which version to clone, you can get the list of all versions for your property.
Sample Response:

Step 6.5: Clone the current version of your property

Request Body:
PROPERTY_VERSION_TO_CLONE is the version number of the version you want to clone. For example, if you want to clone the version 2 of your property, set this value to 2.
Sample Response:

Step 6.6: Remove existing Fingerprint artifacts (if needed)

If your Akamai property already has the Fingerprint proxy integration installed, manually remove the Fingerprint artifacts before updating the integration. Otherwise, some artifacts will be duplicated and the integration will not work.
  1. Navigate to Akamai Control Center → Properties.
  2. Find the cloned property version.
  3. Click Edit to begin editing rules.
  4. Navigate to the Variables section and remove all variables that start with PMUSER_FPJS_.
  5. Scroll to the bottom of the rule tree and delete the rule named Fingerprint.
  6. Click Save to confirm the cleanup.

Step 6.7: Patch the new version with Fingerprint integration rules

Finally, send a PATCH request to update your property’s rule tree with the Fingerprint integration rules:
  • Request body: Copy-paste the content of the dist/patch-body/body.json file you created in Step 5.
  • Content-type: header application/json-patch+json
Sample Response:

Step 6.8: Activate the Patched Version

  • Request body:
PROPERTY_VERSION_TO_ACTIVATE is the version number of the version you previously cloned. For example, if you cloned version 2 of your property and created version 3, set this value to 3.
Please do not forget to replace NOTIFY_EMAIL_ADDRESS_ABOUT_ACTIVATION_STATUS with your email address.
Sample Response:
This will directly activate the version in PRODUCTION. If you want to deploy to staging first, change the network value to STAGING.

Troubleshooting API requests

If you encounter an error, check the following:

Step 7: Configure the Fingerprint client agent

Please see the main Akamai proxy integration guide to Configure the client agent on your website or mobile app.