Api integration
API integration is the connection of software components through application programming interfaces so they can exchange data or invoke functionality.
Build AI-Enhanced Web Apps
The connection of an application to external application programming interfaces to access their functionality or data.
- How it is used
- Connects generative AI web applications to external providers, model capabilities, and supporting data or functionality.
- How deep it goes
- Explains pipelines, provider abstraction, streaming concerns, and integration guidelines without detailing provider-specific request implementations.
- Examples
- Uses JavaScript, React, Next.js, Vercel AI SDK, generateText, streamText, useChat, and useCompletion as integration examples.
- What you can do after
- Apply it via Next.js and the Vercel AI SDK to connect applications with AI providers and deliver generated or streamed responses.
Read how Build AI-Enhanced Web Apps explains api integration →
The Art of AI Product Development
API integration is the incorporation of functionality or data from a software service through its application programming interface.
- How it is used
- Connects pretrained AI models and existing components to user-facing products, applications, and workflows.
- How deep it goes
- Positions integration as a practical AI-engineering task but stops short of detailed implementation code or deployment procedures.
- Examples
- Uses the OpenAI API, LangChain, Hugging Face, vector databases, production systems, and AI-powered workflows as concrete integration contexts.
- What you can do after
- Apply it via named AI tools to build production applications and optimize model interactions.
Read how The Art of AI Product Development explains api integration →
Related concepts
- best practicecontrasts with · A best practice is a generally accepted method or approach regarded as effective for achieving a desired outcome in a particular context.
- contractuses · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.
- RESTuses · REST is an architectural style for distributed hypermedia systems that organizes interactions around resources and representations through constraints including a uniform interface, stateless communication, cacheability, and layered components.
- distributed systemproduces · A distributed system is a computing system whose components run across multiple networked processes or machines and coordinate through communication.
- gRPCuses · gRPC is an open-source remote procedure call framework for defining services and invoking them across process or network boundaries, commonly using Protocol Buffers and HTTP/2.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

