|API reference (SmartDocs) | Policy reference | Other reference
|Get an overview of API and app developer tools and quickly access their docs.|
|Walk through useful end-to-end scenarios that illustrate using Apigee to create powerful APIs.|
Move through a guided development and configuration workflow, from the fundamentals of building APIs to more advanced topics and use cases.
|Learn how to secure your environment and your APIs with OAuth, API keys, content-based security, SSL, admin user and role management, and other security features.|
|Use Apigee's built-in dashboard analytics charts to monitor executive-level metrics such as API traffic and top-performing apps and developers. Gather detailed metrics on the performance of individual APIs, and create custom reports to view and compare the metrics you care about most. Use the analytics tools to troubleshoot issues with your APIs.|
|After you create the APIs you want developers to use, package the APIs as products and make them available to developers. Publish your API documentation, and using an out-of-the-box portal provided by Apigee, build out a community where developers can learn about your APIs, create blog posts, and participate in forums.|
|Generate revenue for the use of your APIs with monetization. Create rate plans for developers to choose from, track API usage, generate billing documents, and provide built-in developer monetization self-service on your Apigee developer portal.|
|As an app developer, you can quickly integrate valuable features into your apps, including social graphs, user management, data storage, push notifications, performance monitoring, and more.|
|Build APIs the right way from the start using best practices.|
|Start with code that works! Deploy and use samples that illustrate the power of Apigee Edge and help get you started with your own API development.|
Help or comments?
- If something's not working: Ask the Apigee Community or see Apigee Support.
- If something's wrong with the docs: Send Docs Feedback
(Incorrect? Unclear? Broken link? Typo?)