You are viewing the Apigee Management API reference documentation. For the main product docs, and to search all docs, go to https://docs.apigee.com. |
Resource files API
API Platform Base Path: https://api.enterprise.apigee.com/v1/o/{org_name}
API Resource Path: /resourcefiles |
A files containing executable code or definitions used by API policies to enable custom behavior and extensibility |
Resource files are executable code or other types of assets (for example XSLT) that are used by API proxies at runtime. Resource files can be stored at one of three levels:
Resource files are resolved by name. Apigee Edge resolves resource files from most specific (API proxy) to the most general (organization). This enables you to store generic code that provides utility processing at the organization level. This provides for greater maintainability, since generic code is not repeated across multiple API proxies. A good example of code that might be scoped to the organization is a library to do Base64 encoding. The following list shows the list of supported resource types and their associated directory name:
For more on resource files, see Resource Files. |
Help or comments?
- If something's not working: Ask the Apigee Community or see Apigee Support.
- If something's wrong with the docs: Click the "Send Feedback" button.
(Incorrect? Unclear? Broken link? Typo?)