The lifecycle at Apigee: how to optimise it within APIQuality

/ apiops, APIs / By

Managing APIs in Apigee can become complex when deployments are manual, there are no clear standards, and each team works ‘their own way’. In an APIQuality webinar, its CEO, Marco Antonio Sanz, shows how to accelerate and standardise the API lifecycle in Apigee by applying an API as Code approach with a visual layer over repositories.

API as Code: the approach that simplifies Apigee

APIQuality is presented as a tool based on the APIs as Code concept, meaning that the lifecycle of an API is managed from repositories, but with a visual layer that facilitates operation.

This allows you to:

  • Centralise common configurations and policies (governance/architecture).
  • Reduce manual work by automatically generating structure and flows.
  • Make repeatable deployments in CI/CD using service accounts.
  • Allow less experienced Apigee users to deploy without touching ‘complex code’.

API lifecycle in Apigee

Learn how to deploy APIs in Apigee quickly and in a standardised manner with APIQuality.

The essentials of Apigee: API Proxy and Target

To understand automation, the webinar recalls the basics of Apigee:

  • API Proxy: a project that defines policies and flows (quotas, security, transformation, etc.).
  • Target: defines the backend to which the API connects (URL, SSL, certificates, additional configuration).

In other words: Apigee is a flow engine, where the proxy controls behaviour before and after calling the target.

The API lifecycle in Apigee within APIQuality: stages and maturity

APIQuality proposes different levels of maturity when integrating an API Manager (in this case, Apigee). For Apigee, the webinar focuses on a lifecycle with typical phases:

  1. Initialise/Templater (pre-configuration): generates the API Proxy with structure, common policies, and flows.
  2. Validate: validates that what is to be deployed is correct (lint, rules, backward compatibility, etc.).
  3. Deploy: automated deployment to Apigee.
  4. (In development) Domain configuration and future phases related to new connectors.

In addition, the roadmap is mentioned: support for more platforms and functionalities such as MCP lifecycle and API Market connectors.

Templates: true standardisation for security and policies

One of the strengths of the webinar is the idea that architecture/governance defines templates, and design teams simply select them.

Examples of common policies that are applied with templates:

  • Security (API Key or OAuth, as appropriate).
  • Quotas (e.g. 200 requests/day).
  • Message transformation/processing rules.
  • Common policies by organisation.

In addition, APIQuality incorporates a template lifecycle:

  • Create new templates.
  • Deprecate old templates.
  • Delete those that are no longer used.

This fits very well with evolving organisations (changes in standards, security, product, etc.).

Target configuration: the only thing that cannot be guessed

The webinar is clear: the tool can automate a lot, but there is something that does require human decision-making:

Which backend the API connects to (Target)

APIQuality allows you to configure:

  • Proxy basepath.
  • Target as a direct URL or as a ‘defined target’.
  • Additional configuration (SSL, certificates, backend specifics).

This is injected into the ‘Target’ part of the generated project.

Live test: deployment + call from Postman

In the demo:

  • The API Proxy is deployed in Apigee.
  • An Apigee product is created (manually, for now) to enable consumption.
  • An app is created to obtain credentials.
  • It is tested in Postman using API Key.

A technical detail is also mentioned regarding encoding between Apigee and Microcks (mocking), and that they will add a recommended default policy to avoid friction when testing mocks.

Conclusion: a faster, governed, and replicable Apigee lifecycle

This approach provides a very powerful idea for teams working with Apigee:

  • Governance and architecture define standards (templates, policies, rules).
  • API teams implement with API First using OpenAPI.
  • APIQuality automates generation, validation, and deployment, reducing dependence on specialists and accelerating time-to-production.

If your organisation is looking to industrialise the API lifecycle in Apigee, reduce errors and standardise security/policies, this ‘API as Code + visual layer + templates’ model is a clear path to scaling.

Try APIQuality for free and discover more features like Apigee

Fill out a short form and access your free demo

Request a free demo