By default, response data features various ID values with three-letter prefixes to help distinguish their function:
aid_forassetIdact_foraccountIdatv_foractivationIdcpc_forcpcodeIdctr_forcontractIdehn_foredgeHostnameIdgrp_forgroupIdmsg_formessageIdprd_forproductIdprp_forpropertyIdinc_forincludeId
Common product IDs
For most operations on properties, you need to get the ID for the specific Akamai product you are using. Some identifiers may not match the current set of product names used for marketing. These are commonly used IDs for different products:
| Product | Code |
|---|---|
| Web Performance Solutions | |
| Dynamic Site Accelerator | prd_Site_Accel |
| Ion Standard | prd_Fresca |
| Ion Premier | prd_SPM |
| Dynamic Site Delivery | prd_Site_Del |
| Rich Media Accelerator | prd_Rich_Media_Accel |
| IoT Edge Connect | prd_IoT |
| Security Solutions | |
| Kona Site Defender | prd_Site_Defender |
| Media Delivery Solutions | |
| Download Delivery | prd_Download_Delivery |
| Object Delivery | prd_Object_Delivery |
| Adaptive Media Delivery | prd_Adaptive_Media_Delivery |
Remove prefixes
While these prefixes may help when exchanging data within PAPI, other Akamai APIs that share the same data don't use this convention. There are two ways to strip them out of data:
-
Run Update client settings to set
"usePrefixes":falseas the default for all requests. This solution is persistent for each API client. -
You can temporarily override the client's default setting by including a
PAPI-Use-Prefixesboolean header with each request. So if the client's settings are"usePrefixes":true, passing in aPAPI-Use-Prefixes: falseheader removes the values.
Both of these options determine whether ID prefixes appear in response data. However, you can always specify any of these IDs as input parameters or JSON data with or without the prefixes.
