Blog Header Image: users on laptops

Announcing Key PAPI Improvements

October 9, 2017 · by Jay Sikkeland ·

We continue to add features and improve the developer experience for the Property Manager API (PAPI), and here are the recent key improvements you should be aware of:

Improved Search – The search endpoint now includes properties that have not yet been activated.  Search allows you to retrieve a particular property (by property name, hostnames and edge hostnames) without traversing the entire group hierarchy.

Activation Control – For better control around activations, PAPI now supports fast fallback and early validation. Furthermore, fast activation (~2 minutes on staging and ~10 minutes on production) has recently been made available to all customers, and is the default for all config changes unless you're adding or removing hostnames.

Custom Behaviors – The ability to reuse advanced metadata via PAPI is included.  Stay tuned for the upcoming official release of Custom Behaviors for Property Manager and PAPI (coming shortly).

Validate Only Option - You can now submit a new config rule tree for validation without creating a new property version.

Optional Resource Prefixes - Resource prefixes (prp_1234, ctr_5678 etc) are now optional, making it easier to build applications across PAPI and other Open APIs.

Optional groupId and contractId - groupId and contractId query parameters are now optional for most PAPI endpoints.

A reminder on Rule formats:  Rule format v2017-06-19 was released a few months ago and has the most up-to-date list of Property Manager features. If you are not already using a fixed rule format, you should do so to prevent Akamai feature changes from breaking your code. See the PAPI documentation on how to "Freeze a Rule Tree’s Feature Set" for more details We intend to release a new rule format roughly every six months.

All these improvements are fully backward-compatible, so the PAPI version number stays on v1.

Jay Sikkeland is a senior product manager at Akamai Technologies.