Resources

API and integration glossary

Plain-language definitions of the API, integration and deployment terms used on the Jundago public website.

API: An interface that lets one piece of software request information or an operation from another.
MCP: Model Context Protocol: a protocol for making tools and resources available to AI applications.
Low-code integration: Connecting systems using configured steps and mappings, with code where it is needed.
REST: An approach to designing interfaces around resources and standard HTTP operations.
GraphQL: A query language and execution model where callers request fields from a defined schema.
gRPC: A framework for calling service methods, commonly using Protocol Buffers to describe messages and operations.
SOAP: A messaging protocol that exchanges structured XML messages.
OpenAPI: A machine-readable description of an HTTP API's operations, inputs, responses and security requirements.
RBAC: Role-based access control: assigning permissions through roles.
ABAC: Attribute-based access control: deciding access from properties of the caller, resource and request.
Runtime: The software environment that executes a service.
Gateway: A service that receives API traffic and applies routing or other request policies.
BYOC: Bring your own cloud: deployment into a customer-owned cloud environment. Confirm whether this means generated services or the full platform.
Dead-letter handling: Keeping messages that could not be processed so they can be inspected and handled later.

Explore this with your team

Bring your data sources, existing services and deployment requirements. We can walk through the workflow together.