Zuplo Changelog

Developers can use Zuplo's CLI and API to automate tasks with the Zuplo platform. For example, you can create a custom CI/CD process to publish your Zuplo API or automate the management of environment variables. Previously, each account had only a single API key, which granted full access to all resources and functionality. With Fine-Grained API Keys, you can create multiple API keys with limited permissions.

These new capabilities allow:

• Create API keys with specific permissions for specific tasks, environments, or projects.
• Set expiration dates on API Keys to ensure that they are only valid for a limited time.
• Administrators can view and manage all API keys in the Zuplo portal to maintain security of their resources.

See the Zuplo API Key documentation for more information.

Over the past month, we have made several improvements to the API Monetization beta:

• Better Error Handling for Stripe Webhooks: We have improved the error handling for Stripe webhooks to ensure more robust and reliable operation.

• Improved Documentation: We have updated and expanded the documentation to provide clearer and more comprehensive guidance.

• Additional Logging: We have added more logging to help diagnose and troubleshoot issues more effectively.

• Editable Plans: We have made plans editable, allowing developers to modify quotas or fix misconfigurations as needed.

These improvements are part of our ongoing effort to refine and enhance the API Monetization beta. We have more enhancements planned before the General Availability (GA) release, and we aim to stabilize the feature in the next month.

We added a new plugin for API Brownouts, which allows developers to simulate outages of their API. This is useful for migrating users off of old versions of their API. You can read more about API Brownouts in our blog post here.

To learn more, please view our Policy documentation.

We have added a new plugin for Curity Phantom Tokens, which allows developers to take advantage of the Curity Identity Management solution. This plugin uses Curity's unique Phantom Token approach which is a privacy-preserving token usage pattern for microservices. It combines the benefits of opaque and structured tokens. To read more about phantom tokens see this document.

To learn more, please view our Policy documentation.

Previously, Zuplo maintained separate infrastructures for development environments (working copy) and production APIs. We have now migrated to a unified infrastructure, where development environments use the same environments as production APIs.

• Consistency: Development environments are now exactly the same as production and preview environments. This ensures that the behavior in development matches that in production, reducing the likelihood of unexpected issues after deployment.

• Global Reach: Development environments are now deployed to over 300 edge locations. This allows developers to test their changes in an environment that closely mimics the distributed nature of our production infrastructure.

• Scalability: Development environments are now fully scalable. This means that they can handle increased load when necessary, providing a more accurate representation of production performance.

• Deployment Time: The trade-off for these benefits is a slightly longer deployment time. However, we are actively working on optimizing our deployment processes to reduce this time.

We believe that the benefits of this change significantly outweigh the trade-offs, and we are excited to see how it improves our development process moving forward.

We are excited to announce the release of API Monetization, a new feature that enables developers to charge for use of their APIs. This feature is available to all Zuplo users and can be configured through the Zuplo Portal. This feature is currently in beta, and we welcome feedback from our users. We aim to make this feature generally available in the coming months.

For more detail see the blog post on API Monetization: API Monetization Release