
Elsevier: Automating API Publishing and Dev Portal Content Deployment
Reduced onboarding time
Elsevier is a global information analytics company, founded in 1880, that provides cutting-edge digital tools for researchers, educators, and healthcare professionals. Within Elsevier, the Enterprise API Management team is responsible for managing the organization’s API platform and developer portal across various business units. Their mission includes onboarding APIs, providing analytics, enforcing governance, and supporting developers through the full API lifecycle.
In this API Summit 2024 presentation, Michelle Barbosa, a Software Engineering Lead on the team, shares how her team uses Kong to streamline API management and developer experience across the organization.
Tackling inconsistencies in developer workflows
Despite having a robust API gateway in place, Elsevier’s API teams encountered multiple challenges during onboarding, which made the process inefficient, slow, and error-prone. Developers needed to learn how to publish APIs on Kong and understand complex plugin configurations for security, rate limiting, and quotas. The manual steps involved in onboarding also made it time consuming and inconsistent across teams. As a result, it became difficult to enforce API governance and collect reliable analytics.
Introducing APIOps
To overcome these challenges, Elsevier introduced APIOps, a framework coined internally to automate API publishing and streamline developer onboarding using Kong. The team created a codebase that automates the full publishing process—from validating OpenAPI specs to deploying declarative configurations to Kong via its Admin API. Using Kong’s decK, Portal CLI, and Insomnia CLI, Elsevier was able to automate the transformation of OpenAPI specs into Kong configurations.
Elsevier also developed a novel "features" system which allows API teams to define plugin configurations like OAuth, rate limiting, and upstream security directly within their API workspace repositories. This makes it easy for developers to configure APIs with the right settings without needing to be experts in Kong’s architecture.
The publishing process is fully integrated into the team’s CI/CD pipeline. A pull request triggers a dry run to generate all necessary configuration files without deploying them. Once merged, the pipeline executes a full deployment, pushing the generated files to Kong’s control plane. Teams are notified via Slack of publishing success or failure, improving transparency and responsiveness.
Delivering impact through smarter processes
The implementation of APIOps led to measurable improvements in both efficiency and visibility:
- 66% Faster Onboarding: API onboarding time was reduced from three days to just one day, significantly accelerating time-to-market.
- Improved Developer Experience: Automation removed the need for developers to manually learn Kong configurations, making onboarding smoother and less error-prone.
- Enhanced API Governance: Standardized validation and deployment ensured governance rules were consistently enforced.
- Comprehensive Analytics: Elsevier now has better visibility into API consumption, enabling data-driven monetization strategies across the platform.
“APIOps has significantly alleviated the pain points of our API teams…reducing onboarding time from three days to just one. We’ve accelerated go-to-market, enhanced analytics, and improved monetization strategies for Elsevier APIs across the board.”