API reference getting started

Using the Edge management API

All Apigee Edge services can be configured through a RESTful API called the Edge management API. That means you can use scripts to create, configure, and manage API proxies and API products, create and manage apps and app developers, and to perform many other types of operations progamatically, using any HTTP client. The API resources exposed by the Edge management API support JSON and XML, and are secured via HTTP Basic Authentication. You need to provide the email address and password associated with your organization on Apigee Edge with each API call that you make.

Following RESTful principles, you can call HTTP GET, POST, PUT, and DELETE methods on any of the API resources.

Every page of the API Reference contains an example cURL command that lets you try out the API.

Along with cURL, you can use the Apigee Console. The console provides a GUI for exploring an API's resources and executing its methods. The Console is pre-populated with information about the Edge management APIs that enables you to make a request to the API from your web browser. The Console also contains contextual links to the API Reference so that you can find out more information about each API as you try it out.

Authentication

In the previous cURL example, notice the required -u email:password. Your Apigee account includes a username and email, along with a password. While you can log into the Edge management UI with your username, you must make management API calls with your Apigee account email address. Your username will not work in management API calls.

About Core Persistence Services

Apigee is moving to a microservices-based product architecture, which will improve the way we develop and deliver products. One of the microservices is called "Core Persistence Services" (CPS), which handles management of various entities in Apigee Edge, such as developers, apps, and key/value maps.

As part of the CPS rollout, certain customers will have CPS enabled in their organizations. That means certain management APIs will either be new or behave a little differently. CPS is enabled with an organization-level property called features.isCpsEnabled. You can check for the presence of this and other organization-level properties by running the following API call with organization administrator credentials: