Latest commit 1a9a9a6 Oct 14, 2016 @floydjonz floydjonz 160921 cloud release
Includes Shared Flows and a new Flow Callout policy
Failed to load latest commit information.
policy 160921 cloud release Oct 13, 2016

Working with schemas

In Apigee Edge, API proxies, policies, and other entities are configured in XML. Use these schemas to help construct your XML configurations, either as reference material or imported into an XML editing environment.

/configuration - Contains the schemas for other-than-policy entities in Edge, such as API proxies, proxy endpoints, target endpoints, HTTP target connections, and so on.

/policy - Contains the schemas for Edge policies.

Importing all.xsd into an XML editing environment lets you construct all entities and policies in a single view; or you can import individual policy schemas to build single policies.

Note: Some policies, such as Message Logging and LDAP, have elements in the /configuration/configuration_schemas.xsd schema as well. This is a known issue that Apigee will address in the future. In the meantime, consult the policy reference docs for guidance.

Bug: There is a known bug where some schemas enforce a specific element order. In each policy, all direct child elements can be used in any order.

Ask the community

alt text

Copyright © 2016 Apigee Corporation

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.