Why I Prefer Option API: Key Advantages Explored

In the ever-evolving tapestry of the digital world, where every application, service, and device strives for seamless communication, the humble Application Programming Interface, or API, has emerged as the undisputed backbone. It is no exaggeration to state that the modern digital economy is fundamentally an API economy, powered by intricate networks of interconnected software components exchanging data and invoking functionalities across vast digital landscapes. For developers, architects, and business strategists alike, the decision to leverage well-designed, robust APIs – what I term the "Option API" paradigm – is not merely a technical preference but a strategic imperative that unlocks unparalleled flexibility, scalability, and innovation. This article delves deep into the myriad advantages of embracing this API-centric approach, exploring how the strategic deployment of apis, fortified by advanced tools like the api gateway and standardized by specifications such as OpenAPI, fundamentally transforms how we build, deploy, and manage digital services.

The choice to wholeheartedly adopt the "Option API" framework signifies a conscious pivot away from monolithic, tightly coupled systems towards a decentralized, modular architecture. It champions the principle of services exposing their capabilities through clearly defined, accessible interfaces, thereby fostering a vibrant ecosystem of interoperability. This strategic embrace is driven by the undeniable benefits of agility in development, enhanced security postures, unprecedented scalability, and the boundless potential for fostering an innovative developer community. As we peel back the layers of this powerful paradigm, we will uncover how this preference translates into tangible gains for businesses and a more streamlined experience for developers, setting the stage for future-proof digital infrastructure that can adapt and thrive amidst continuous technological disruption.

The Foundational Power of APIs: Unlocking Connectivity and Innovation

At its core, an API is a set of defined rules that dictates how software components should interact with each other. It acts as an intermediary, allowing different applications to talk to one another without needing to understand the underlying implementation details. Imagine it as a standardized menu in a restaurant: you don't need to know how the chef prepares the dish, only what ingredients are available and how to order it. Similarly, an API abstracts complexity, providing a clean, consistent interface for consuming services. This abstraction is the bedrock of modern software development, enabling independent teams to develop disparate components that seamlessly integrate into a cohesive system.

Historically, software systems were often monolithic, with all functionalities bundled into a single, large application. Updates were cumbersome, scaling was challenging, and innovation was stifled by the tight coupling of components. The advent of distributed systems, and more recently, microservices architectures, has revolutionized this landscape. In this new paradigm, functionalities are broken down into smaller, independent services, each communicating with others exclusively through their APIs. This shift has not only dramatically increased development velocity but has also fundamentally altered the economics of software, giving rise to what is now widely recognized as the API economy. Businesses no longer need to build every service from scratch; they can consume specialized APIs from third-party providers for functionalities like payment processing, mapping, communication, or machine learning, integrating these capabilities into their own offerings with relative ease.

The transformative power of an API extends far beyond mere technical integration. It fundamentally enables new business models and accelerates product development cycles. Consider the proliferation of mobile applications that leverage mapping services like Google Maps, payment gateways like Stripe, or social media integrations. None of these applications would be feasible without robust and accessible APIs exposing these complex services in a consumable format. Businesses can rapidly prototype and deploy new features by assembling existing API components, significantly reducing the time-to-market for innovative products and services. This reusability of software components, exposed through well-defined APIs, translates directly into reduced development costs and increased operational efficiency, freeing up valuable engineering resources to focus on core business logic and truly differentiate their offerings. Moreover, the inherent decoupling fostered by an API-first approach means that different parts of a system can be developed, deployed, and scaled independently, minimizing dependencies and reducing the risk of cascading failures, thereby enhancing the overall resilience of the digital infrastructure. The clarity and predictability offered by a well-documented API also empower developers to integrate faster and with fewer errors, driving adoption and fostering a more dynamic and collaborative development environment across the entire digital value chain.

Enhancing API Management with API Gateways: Security, Performance, and Control

While the intrinsic value of an API is undeniable, exposing raw backend services directly to a multitude of clients, especially external ones, can quickly become a security and management nightmare. This is where the API Gateway emerges as an indispensable architectural component, acting as a single entry point for all API calls. It sits between the client applications and the backend services, intelligently routing requests, enforcing policies, and providing a crucial layer of abstraction and control. Without an api gateway, managing aspects like authentication, authorization, rate limiting, and monitoring across dozens or hundreds of individual services would be an overwhelmingly complex and error-prone endeavor, diluting the very advantages that apis are meant to provide.

The primary functions of an API Gateway are multi-faceted and critically important for any scalable and secure API ecosystem:

• Authentication and Authorization: The api gateway is the first line of defense, verifying the identity of the calling application or user and ensuring they have the necessary permissions to access the requested resource. This centralized security enforcement simplifies backend service logic, allowing them to focus purely on business functionality.
• Rate Limiting and Throttling: To prevent abuse, manage traffic, and ensure fair usage, api gateways can enforce limits on the number of requests a client can make within a specified timeframe. This protects backend services from being overwhelmed and ensures service stability.
• Traffic Routing and Load Balancing: An api gateway can intelligently route incoming requests to appropriate backend services based on various criteria, such as API version, request path, or even the health of the target service. It can also distribute traffic across multiple instances of a service, ensuring high availability and optimal resource utilization.
• Caching: By caching frequently accessed responses, the api gateway can reduce the load on backend services and significantly improve response times for clients, leading to a better user experience and reduced operational costs.
• Request/Response Transformation: It can modify incoming requests or outgoing responses, adapting them to the specific needs of clients or backend services. This might involve translating data formats, adding or removing headers, or restructuring payloads, making it easier to evolve services independently without breaking client compatibility.
• Monitoring and Analytics: A robust api gateway provides comprehensive logging and metrics on api usage, performance, and errors. This data is invaluable for troubleshooting, capacity planning, and understanding how apis are being consumed, offering critical insights into the health and efficiency of the entire API ecosystem.

The strategic implementation of an api gateway streamlines client-side logic immensely. Instead of needing to know the specific endpoints and authentication mechanisms for each individual backend service, clients only interact with the api gateway's single, unified interface. This abstraction makes it far easier to evolve backend services, refactor architectures, or even migrate services without impacting client applications, fostering greater agility and reducing maintenance overhead.

For organizations managing a growing portfolio of apis, especially those incorporating cutting-edge technologies like AI, an advanced API Gateway becomes an absolute necessity. Consider a platform like ApiPark, which serves as an open-source AI gateway and api management platform. It exemplifies the robust capabilities an api gateway can offer beyond basic routing. APIPark addresses specific challenges in the AI era by providing quick integration for over 100 AI models, a unified API format for AI invocation (which means changes in AI models or prompts don't break your application), and the ability to encapsulate prompts into REST apis. This functionality significantly simplifies the development and maintenance costs associated with leveraging complex AI services.

Furthermore, APIPark highlights critical api gateway features for comprehensive lifecycle management – from design and publication to invocation and decommission. It allows for the regulation of API management processes, managing traffic forwarding, load balancing, and versioning of published apis. Its performance rivaling Nginx, with capabilities to achieve over 20,000 TPS on modest hardware, underscores the importance of a high-performance api gateway in handling large-scale traffic. The platform's emphasis on detailed API call logging and powerful data analysis provides businesses with the crucial visibility needed for troubleshooting, security auditing, and preventive maintenance, ensuring system stability and data security. By centralizing API service sharing within teams and enabling independent apis and access permissions for each tenant, APIPark demonstrates how a well-implemented api gateway transforms chaotic API sprawl into a well-governed, efficient, and secure digital asset. This holistic approach to api management through a powerful api gateway truly embodies the advantages of the "Option API" preference, elevating apis from mere technical interfaces to strategic business enablers.

Here's a summary of the core benefits provided by a robust API Gateway:

Feature Category	Specific Benefit	Impact on API Ecosystem
Security	Centralized Authentication & Authorization	Prevents unauthorized access; simplifies security enforcement.
	Threat Protection (DDoS, injection)	Safeguards backend services from malicious attacks.
Performance	Rate Limiting & Throttling	Ensures fair usage, prevents overload, maintains service stability.
	Caching	Reduces latency, offloads backend services, improves user experience.
	Load Balancing	Distributes traffic efficiently, ensures high availability.
Management	Unified Entry Point & Routing	Simplifies client interaction; flexible backend evolution.
	Request/Response Transformation	Adapts interfaces for compatibility; facilitates versioning.
	Monitoring & Analytics	Provides insights into API usage, performance, and errors.
	Lifecycle Management	Governs API from design to deprecation; ensures consistency.
Developer Experience	Simplified Integration	Reduces complexity for developers consuming APIs.
	Consistent Interface	Enhances predictability and reduces integration errors.

Standardizing API Design with OpenAPI: Clarity, Collaboration, and Automation

The efficacy of the "Option API" paradigm hinges not just on the availability of APIs or the presence of an API Gateway, but critically on the quality, consistency, and discoverability of the apis themselves. A poorly documented or inconsistently designed API can quickly negate all the advantages of an API-first strategy, leading to developer frustration, integration errors, and increased time-to-market. This is precisely where the OpenAPI Specification (OAS), formerly known as Swagger Specification, steps in as a game-changer. OpenAPI is a language-agnostic, human-readable, and machine-readable interface description language for defining RESTful apis. It provides a standard way to describe the operations, parameters, authentication methods, and data models of an api, acting as a blueprint for how a API works.

The benefits of adopting the OpenAPI Specification are profound and far-reaching, fundamentally enhancing the clarity, collaboration, and automation capabilities within an api-driven development environment:

• Clear, Comprehensive Documentation: OpenAPI allows for the creation of interactive, live documentation that developers can explore, understand, and even test directly from a web browser. This eliminates the need for manual, often outdated, documentation, ensuring that the API's contract is always accurate and accessible. The machine-readable nature of OpenAPI means that this documentation can be automatically generated and kept in sync with the API's implementation, reducing discrepancies and improving developer confidence.
• Facilitates Client and Server Stub Generation: One of OpenAPI's most powerful features is its ability to generate client SDKs (Software Development Kits) in various programming languages and server stubs from a single API definition. This significantly accelerates development by providing pre-built code that handles the nuances of api interaction, allowing developers to focus on application logic rather than boilerplate code for API calls.
• Enables Automated Testing: With a formal OpenAPI definition, it becomes straightforward to automate the testing of apis. Tools can read the specification and generate test cases, perform validation against the defined schema, and even simulate various api behaviors, ensuring the API functions as expected and remains consistent across updates. This dramatically improves the quality and reliability of APIs while reducing manual testing effort.
• Improves Developer Experience (DX): A well-defined OpenAPI specification is a gift to developers. It provides a clear contract, reduces ambiguity, and empowers them to integrate with APIs faster and with greater confidence. This enhanced developer experience translates into quicker adoption of apis, fostering a more vibrant ecosystem and accelerating innovation both internally and externally.
• Supports API Discovery: For organizations managing a large number of internal and external apis, OpenAPI acts as a common language that makes apis discoverable. Combined with an api gateway that acts as a central catalog, OpenAPI descriptions can be used to populate developer portals, allowing teams to easily find and understand available services, promoting reuse and reducing redundant development efforts.
• Fosters Better Collaboration: OpenAPI serves as a universal language that bridges the communication gap between different teams involved in the API lifecycle—from front-end and back-end developers to QA engineers and product managers. Everyone can refer to the same, unambiguous OpenAPI definition, ensuring a shared understanding of the API's behavior and requirements, thereby streamlining collaboration and reducing miscommunications.

The adoption of OpenAPI inherently drives an API-first design philosophy. Instead of building the backend logic and then retrofitting an API, OpenAPI encourages defining the API contract before implementation. This ensures that the api is designed with the consumer in mind, promoting usability, consistency, and a clear separation of concerns. Furthermore, the OpenAPI specification can be integrated seamlessly with api gateways. An api gateway can validate incoming requests against the OpenAPI schema, automatically enforce policies based on the api definition, and even dynamically generate developer portals, creating a highly integrated and efficient api management ecosystem. By embracing OpenAPI, organizations cement their preference for well-structured, discoverable, and easily consumable apis, laying a solid foundation for sustainable growth and innovation in the digital sphere. The clarity and tooling ecosystem built around OpenAPI are essential for any organization serious about scaling its API strategy and empowering its developers.

APIPark is a high-performance AI gateway that allows you to securely access the most comprehensive LLM APIs globally on the APIPark platform, including OpenAI, Anthropic, Mistral, Llama2, Google Gemini, and more.Try APIPark now! 👇👇👇

The Strategic Advantages of Adopting the "Option API" Paradigm

The deliberate choice to embrace the "Option API" paradigm, underpinned by robust apis, intelligent api gateways, and standardized OpenAPI specifications, delivers a multitude of strategic advantages that collectively drive business growth, operational efficiency, and sustained innovation. This approach is not merely about individual technical components but about a holistic architectural philosophy that prioritizes flexibility, security, and the creation of value through interconnected services.

Flexibility and Agility

One of the most compelling reasons to prefer the "Option API" is the unparalleled flexibility and agility it injects into software development and deployment. By defining clear API contracts, services become decoupled, meaning changes to one service's internal implementation do not necessarily impact other services as long as its API contract remains stable. This architectural independence allows teams to develop, test, and deploy services asynchronously and at their own pace, significantly accelerating development cycles. When a new feature is required, or an existing service needs an update, only the relevant service needs to be modified and redeployed, rather than the entire monolithic application. This microservices-oriented approach, enabled by robust apis, makes organizations far more responsive to market demands and capable of rapid experimentation and iteration. The ability to swap out or upgrade individual components without causing ripple effects across the entire system means businesses can innovate faster, reducing the time from concept to market and staying ahead of competitors.

Scalability

The "Option API" paradigm inherently fosters greater scalability. Each service, exposed via its own api, can be scaled independently based on its specific load requirements. If the authentication service experiences a surge in demand, only that service needs additional resources, not the entire application. This targeted scaling is far more efficient and cost-effective than scaling a monolithic application, which often requires replicating the entire codebase even if only a small part is under strain. An api gateway further enhances this by providing advanced load balancing capabilities, intelligently distributing incoming traffic across multiple instances of backend services, ensuring optimal performance and preventing bottlenecks. This granular control over resource allocation allows organizations to handle massive traffic fluctuations and unpredictable growth patterns without incurring unnecessary infrastructure costs or compromising service availability.

Security

Security is paramount in the digital age, and the "Option API" approach, especially when combined with a sophisticated api gateway, offers significant advantages in this domain. A centralized api gateway acts as a crucial security enforcement point, allowing for the consistent application of security policies such as authentication, authorization, encryption, and threat detection across all apis. Instead of scattering security logic across numerous backend services, it is consolidated and managed at the gateway layer, simplifying auditing, reducing attack surfaces, and ensuring that every incoming request meets stringent security criteria before reaching sensitive backend systems. Features like subscription approval (as offered by APIPark, requiring callers to subscribe and await administrator approval before invocation) add an extra layer of control, preventing unauthorized calls and potential data breaches. This centralized approach significantly strengthens the overall security posture, making it easier to identify and mitigate vulnerabilities and maintain regulatory compliance.

Developer Experience (DX)

For any API ecosystem to thrive, it must offer an exceptional developer experience. The "Option API" paradigm, especially when leveraging OpenAPI specifications, elevates DX to a new level. Well-documented apis with clear contracts, easy-to-use SDKs (often generated from OpenAPI), and consistent error handling empower developers to integrate faster, with fewer roadblocks and greater confidence. Interactive documentation portals, facilitated by OpenAPI tools, allow developers to explore api capabilities, test endpoints, and understand data models intuitively. This reduces the learning curve, minimizes support requests, and allows developers to focus on building innovative applications rather than wrestling with obscure integration challenges. A positive DX fosters a vibrant developer community, both internal and external, which in turn drives the adoption and innovation around an organization's api offerings.

Ecosystem Development

The true power of APIs extends beyond internal integration; it lies in their potential to foster external partnerships and create entirely new business ecosystems. By exposing stable, well-documented apis, businesses can enable third-party developers, partners, and even competitors to build on top of their platforms, extending their reach and creating new revenue streams. Think of app stores, payment networks, or specialized service marketplaces—all built upon the foundation of accessible apis. The "Option API" approach facilitates this by providing the necessary technical framework for secure, scalable, and manageable external integrations, turning products into platforms and fostering a network effect that drives exponential growth and innovation across industries.

Cost Efficiency

Embracing the "Option API" strategy ultimately leads to significant cost efficiencies. The reusability of services exposed through apis reduces redundant development efforts. Faster development cycles and reduced time-to-market mean quicker returns on investment. Targeted scaling, facilitated by api gateways, optimizes infrastructure spending by allocating resources precisely where needed. Streamlined API management, detailed logging, and performance analytics reduce operational overhead and simplify troubleshooting. Moreover, by leveraging third-party APIs for non-core functionalities (e.g., payment, maps, AI models), businesses can avoid the substantial costs associated with building and maintaining these complex systems in-house, allowing them to allocate resources more strategically to their core competencies.

Future-Proofing

Finally, the "Option API" paradigm provides a robust foundation for future-proofing digital infrastructure. By decoupling services and abstracting their implementations behind stable API contracts, organizations gain the flexibility to adopt new technologies, migrate to different cloud providers, or refactor backend services without disrupting client applications. This architectural resilience ensures that systems can adapt to evolving business requirements, emerging technologies (like new AI models that can be seamlessly integrated via an api gateway like APIPark), and changing market demands, protecting investments and ensuring long-term relevance in an unpredictable digital landscape. The ability to swap out backend implementations without affecting the API contract means that technological evolution can occur continuously and iteratively, preventing the accumulation of technical debt and ensuring that the platform remains agile and modern.

Challenges and Considerations

While the "Option API" paradigm offers undeniable advantages, its successful implementation is not without challenges. Adopting an API-first strategy requires careful planning, robust governance, and continuous attention to detail. Overlooking these critical considerations can undermine the benefits and lead to complexity, security vulnerabilities, or a degraded developer experience.

One of the primary challenges lies in designing effective APIs. A well-designed api is intuitive, consistent, and provides clear error handling. This is more difficult than it sounds. Considerations like API versioning (how to evolve an api without breaking existing clients), proper resource modeling, choosing appropriate HTTP methods, and crafting meaningful error messages require significant thought and adherence to best practices. Without a consistent design philosophy, developers consuming different apis within the same organization might face a disjointed and frustrating experience, negating the benefits of standardization. Tools that facilitate OpenAPI driven design-first approaches can significantly mitigate this by enforcing consistency from the outset.

Another significant consideration is governance and lifecycle management. As the number of apis grows, so does the complexity of managing them. Organizations need clear processes for api design, approval, publication, monitoring, and eventual deprecation. Without a centralized system to oversee this lifecycle, apis can become orphaned, redundant, or outdated, leading to an uncontrolled "API sprawl." This is where a comprehensive api management platform becomes crucial. Platforms like APIPark, which offer end-to-end api lifecycle management, assist in regulating these processes, ensuring that apis are properly documented, versioned, and retired when no longer needed, maintaining a clean and efficient API ecosystem. The ability to manage independent apis and access permissions for different teams (tenants) also aids in maintaining governance in larger enterprises.

Monitoring and observability are also critical. For an api-driven architecture, understanding the real-time performance, usage patterns, and error rates of each api is essential for maintaining system health and troubleshooting issues. Without robust monitoring tools, identifying the root cause of a performance bottleneck or an integration failure in a distributed system can be incredibly difficult and time-consuming. An api gateway plays a vital role here by centralizing logging and metrics, offering a single pane of glass into the entire api traffic flow. Detailed api call logging, as provided by APIPark, allows businesses to quickly trace and troubleshoot issues, ensuring system stability and data security. Furthermore, powerful data analysis capabilities are needed to analyze historical call data, predict trends, and perform preventive maintenance before issues impact users.

Security best practices must be rigorously applied across the entire API landscape. Beyond authentication and authorization handled by the api gateway, considerations include data encryption in transit and at rest, protection against common web vulnerabilities (like SQL injection or cross-site scripting), robust input validation, and secure handling of sensitive data. Regular security audits and penetration testing are indispensable. The modular nature of apis means that a vulnerability in one service could potentially be exploited, highlighting the need for a "defense-in-depth" strategy across all layers of the api architecture.

Finally, testing strategies must evolve to accommodate the distributed nature of apis. Unit tests, integration tests, and end-to-end tests for apis become more complex but are more vital than ever. Automation, often driven by OpenAPI specifications, is key to ensuring that apis remain functional and consistent throughout their lifecycle. Without a robust testing framework, changes to one api could inadvertently break integrations with other services, leading to system instability and costly remediation efforts. The complexity of managing numerous apis without the proper tools and governance structure can quickly become overwhelming, underscoring the necessity of investing in api management platforms and embracing a disciplined, api-first approach from the outset.

Conclusion

The preference for the "Option API" paradigm is more than a technical inclination; it is a strategic embrace of an architectural philosophy that champions flexibility, scalability, security, and innovation in the digital age. As we have explored, the fundamental role of robust apis in enabling seamless communication and data exchange is amplified by the capabilities of an intelligent api gateway and standardized by the clarity of OpenAPI specifications. This triumvirate forms the cornerstone of modern, agile, and resilient digital infrastructure.

By strategically choosing to leverage well-designed apis, organizations unlock unprecedented agility, allowing them to respond rapidly to market changes, accelerate product development, and integrate with diverse external services and partners. The api gateway acts as the critical traffic controller and security enforcer, providing a unified entry point, centralizing security policies, and optimizing performance through features like rate limiting, caching, and intelligent routing. This abstraction layer simplifies client interactions and provides invaluable insights through detailed monitoring and analytics. Concurrently, OpenAPI provides the universal language for defining api contracts, driving consistent design, generating accurate documentation, and enabling powerful automation for development and testing, thereby significantly enhancing the developer experience and fostering broader api adoption.

In a world increasingly driven by interconnected services and data flows, the strategic choice for "Option API" is not just about keeping pace; it's about leading the charge. It equips businesses with the tools to build innovative ecosystems, reduce operational costs, and future-proof their digital assets against the relentless tide of technological evolution. The journey towards a truly api-first enterprise may present challenges, from design complexities to governance overhead, but with the right architectural decisions, robust api management platforms like APIPark, and a commitment to OpenAPI standards, the rewards of enhanced efficiency, security, and boundless innovation far outweigh the initial investment. The future of interconnected systems is undeniably api-driven, and choosing the "Option API" is the smartest way to navigate and thrive within it.

---

Frequently Asked Questions (FAQs)

1. What exactly is meant by "Option API" in this context? "Option API" refers to the strategic and conscious decision to prioritize and leverage robust, well-designed Application Programming Interfaces (APIs) as the primary means of communication and integration between software components, both internally and externally. It implies an API-first approach to architecture, favoring the flexibility, scalability, and control offered by modern API ecosystems over tightly coupled systems or less structured integration methods.

2. Why is an API Gateway considered crucial for modern API architectures? An API Gateway is crucial because it acts as a single, centralized entry point for all API calls, sitting between client applications and backend services. It provides essential functionalities such as authentication, authorization, rate limiting, traffic routing, caching, and monitoring. This centralization enhances security, optimizes performance, simplifies API management, and allows for greater control over the entire API ecosystem, preventing direct exposure of backend services.

3. How does OpenAPI Specification contribute to better API management? OpenAPI Specification (OAS) provides a standardized, language-agnostic format for describing RESTful APIs. It contributes to better API management by enabling clear, machine-readable documentation, facilitating the generation of client SDKs and server stubs, and supporting automated testing. This standardization improves developer experience, fosters better collaboration between teams, enhances API discoverability, and ensures consistency and predictability across different APIs.

4. What are the key business advantages of adopting an API-first strategy? Adopting an API-first strategy offers several key business advantages, including increased agility and faster time-to-market for new features and products due to decoupled services. It also improves scalability by allowing independent scaling of services, strengthens security through centralized control via API Gateways, enhances developer experience, fosters ecosystem development by enabling third-party integrations, and ultimately leads to cost efficiencies through reusability and optimized resource allocation.

5. How can platforms like APIPark assist in an API-centric approach? Platforms like APIPark serve as comprehensive AI Gateways and API Management platforms, designed to support an API-centric approach. They assist by offering end-to-end API lifecycle management (from design to deprecation), quick integration of various AI models with unified management, prompt encapsulation into REST APIs, and robust security features like subscription approval. APIPark also provides high performance for large-scale traffic, detailed call logging, and powerful data analysis, all of which are critical for efficiently managing, securing, and scaling an API ecosystem in the modern digital landscape.

🚀You can securely and efficiently call the OpenAI API on APIPark in just two steps:

Step 1: Deploy the APIPark AI gateway in 5 minutes.

APIPark is developed based on Golang, offering strong product performance and low development and maintenance costs. You can deploy APIPark with a single command line.

curl -sSO https://download.apipark.com/install/quick-start.sh; bash quick-start.sh

In my experience, you can see the successful deployment interface within 5 to 10 minutes. Then, you can log in to APIPark using your account.

Step 2: Call the OpenAI API.