> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apinizer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> Explanations of terms used in the Apinizer context. This glossary contains important terms for better understanding and using the platform.

## Basic Concepts

<CardGroup cols={2}>
  <Card title="API" icon="code">
    Application Programming Interface - Application Programming Interface. An interface that facilitates one application 'consuming' the capabilities or data of another application.
  </Card>

  <Card title="API Management" icon="gear">
    The set of operations for managing, formatting, deploying, and related operations of APIs in a secure and scalable environment.
  </Card>

  <Card title="API Lifecycle" icon="circle-nodes">
    The process that includes all steps from the creation of an API idea to its deprecation.
  </Card>

  <Card title="API Gateway" icon="shield">
    The common name for software that provides functions such as security, logging, traffic management, message transformation in front of APIs.
  </Card>
</CardGroup>

<AccordionGroup>
  <Accordion title="API (Application Programming Interface)">
    API (*Application Programming Interface* - Application Programming Interface) is an interface that facilitates one application 'consuming' the capabilities or data of another application. By defining stable, simplified entry points to application logic and data, it enables developers to easily access and reuse application logic created by other developers.

    Today, APIs are widely used as a **contract** that determines the structure of communication between client and server in general or local network environments, mobile or web-based applications. In the Apinizer context, the word API refers to *server-side Web API* with this more limited meaning.
  </Accordion>

  <Accordion title="API Management">
    API management is the set of operations for managing, formatting, deploying, and related operations of APIs in a secure and scalable environment. The goal of API management is to meet the requirements of API stakeholders in a quality and cost-effective manner.

    API management needs may vary from organization to organization, but basic functions such as API security, monitoring, and version control are generally common.

    <Info>
      **Apinizer is an API Management Platform.**
    </Info>
  </Accordion>

  <Accordion title="API Lifecycle">
    All steps of an API from the creation of its idea, determination of its requirements, design and development, testing, deployment and fulfillment of security requirements, support, monitoring of its operation, improvement of its performance, pricing and sale, use, feedback, update, versioning, or deprecation of a version form the API Lifecycle.

    Organizations can customize how they will operate the steps of the lifecycle within the framework of their own needs.

    <Info>
      **Apinizer supports the API Lifecycle and provides a platform where API Stakeholders can work collaboratively within their own roles.**
    </Info>
  </Accordion>

  <Accordion title="API Gateway">
    *API Gateway* is the common name for software that solves many tasks such as security, logging, traffic management, message transformation, protocol conversion, message validation, and similar without touching the API code, by making configuration at an external point.

    It is placed in front of APIs and API message traffic passes through the API Gateway. Thus, all kinds of control, transformation or customization on these messages becomes possible.

    **How API Gateway works:**

    1. The request sent by the client is received by the API Proxy on the API Gateway
    2. API Proxy becomes a client to the API and receives the responses returned by the API
    3. API Proxy returns the responses to the client itself

    Through configurations made with the API Gateway software, the behavior of the API Proxy is customized, and thus requirements such as security, traffic management, message transformations, service migration, and similar can be managed from a central point.

    <Info>
      **Apinizer provides an advanced, easy-to-use, horizontally scalable API Gateway.**
    </Info>
  </Accordion>
</AccordionGroup>

## API Stakeholders

Everyone who is involved in one or more steps of the API Lifecycle is an API Stakeholder.

<CardGroup cols={2}>
  <Card title="API Product Manager" icon="user-tie">
    The role that thinks, determines, and manages the features that the API Product should provide, quality requirements, capabilities, which customer needs it can meet, its cost and sales price, and how it will be marketed.
  </Card>

  <Card title="API Requirements Analyst" icon="user-gear">
    Identifies and documents API requirements.
  </Card>

  <Card title="API Designer" icon="pencil">
    Designs parameters, headers, message structure, and similar details regarding the messages that the endpoints to be provided by the API will receive or return, and publishes these as an API Specification in a format that API Developers can understand and use.
  </Card>

  <Card title="API Developer" icon="code">
    Writes the API code as actual software development work. Creates API Proxies and makes their configuration. Makes configurations for integrations to be performed.
  </Card>

  <Card title="API Test Specialist" icon="flask">
    Tests API Proxies with criteria such as functional correctness, performance, and security.
  </Card>

  <Card title="API Quality Specialist" icon="check-circle">
    Continuously monitors API Proxies or API Products with different criteria such as the level of meeting client needs, correct operation, and performance, identifies necessary improvements, and provides feedback to API Developers.
  </Card>

  <Card title="API Support Specialist" icon="headset">
    Evaluates and resolves API Consumer complaints, requests, or notifications related to API Products, and provides input to API Developers or API Product Manager.
  </Card>

  <Card title="API Portal Administrator" icon="globe">
    Manages the API Portal application where API Products are delivered to API Consumers.
  </Card>

  <Card title="API Analytics Specialist" icon="chart-bar">
    Manages, examines, and reports API logs, and collects metrics such as general performance, error frequency, most problematic or most used APIs, and provides input to API Product Manager or API Developers for necessary improvements and arrangements.
  </Card>

  <Card title="API Security Manager" icon="shield">
    Performs tasks such as managing client identities, determining how and how much sensitive data will be logged, and making password-required connection definitions.
  </Card>

  <Card title="API Consumer" icon="users">
    Acts as a client to API Proxies or purchases and uses API Products.
  </Card>
</CardGroup>

<Info>
  **Apinizer provides the necessary administrative tools and infrastructure for the creation of relevant stakeholders and their ability to work collaboratively with other stakeholders with dynamic role management capabilities.**
</Info>

## Apinizer-Specific Terms

<CardGroup cols={2}>
  <Card title="API Proxy" icon="network-wired" href="/en/concepts/core-concepts/what-is-api-proxy">
    The proxy of an API on the API Gateway. The client actually communicates with the API Proxy.
  </Card>

  <Card title="Policy" icon="shield" href="/en/concepts/core-concepts/what-is-policy">
    Configurable components that define operations applied to messages in API Proxies.
  </Card>

  <Card title="DB-2-API" icon="database">
    Feature for creating APIs from database operations. Provides the ability to create APIs in minutes without writing code.
  </Card>

  <Card title="Script-2-API" icon="code">
    Feature for creating APIs from JavaScript or Groovy code. Provides the ability to instantly open APIs.
  </Card>

  <Card title="Mock API Creator" icon="wand-magic-sparkles">
    Feature for instantly creating Mock APIs without any server or code writing need.
  </Card>
</CardGroup>

<AccordionGroup>
  <Accordion title="API Proxy">
    API Proxy is the proxy of an API on the API Gateway. The client actually communicates with the API Proxy. API Proxy becomes a client to the API and receives the responses returned by the API and returns the response to the Client itself.

    API Proxy provides functions such as security, traffic management, and message transformation without touching the API's business logic.

    For detailed information, see the [What is API Proxy?](/en/concepts/core-concepts/what-is-api-proxy) page.
  </Accordion>

  <Accordion title="Policy">
    Policy is configurable components that define operations applied to messages in API Proxies. Policies provide various functions such as security, validation, transformation, and traffic management.

    Policies are configured and reused with form-based interfaces without writing code.

    For detailed information, see the [What is Policy?](/en/concepts/core-concepts/what-is-policy) page.
  </Accordion>

  <Accordion title="DB-2-API">
    Many applications use APIs developed for database operations that do not require special business logic. Although it is easy to develop this type of API, it is necessary to create a programming environment, have people with developer identities work, deploy the developed APIs to a server, and set up a server for this.

    **Apinizer enables even non-developers to create and deploy a database operation API in minutes with DB-2-API.**

    **Supported Operations:**

    * Native SQL statements
    * Stored Procedure calls
    * Returning cursor results
    * Batch operations

    **Advantages of DB-2-API:**

    * Creating APIs without writing code
    * No need for separate server installation
    * APIs can be deployed in minutes
    * Shortens API development time for database operations
  </Accordion>

  <Accordion title="Script-2-API">
    Some APIs are created to expose an algorithm or to enable a method to be executed by other stakeholders. The algorithm or method may already exist or may need to be newly developed. In both cases, this requires steps such as doing it in a software development environment, packaging the API, and placing it on a server where it will be deployed.

    **Apinizer enables users to instantly open an API by writing (or pasting existing) JavaScript or Groovy code with Script-2-API.**

    **Features:**

    * JavaScript or Groovy code support
    * Use of request/response messages
    * Ability to use desired parts of request/response messages in the code
    * No need for tasks such as setting up a separate server
    * APIs can be deployed in minutes
  </Accordion>

  <Accordion title="Mock API Creator">
    Mock API Creator provides the ability to instantly create Mock APIs without any server or code writing need. It is used for starting frontend development before backend development is completed, testing API design, and in integration tests.
  </Accordion>
</AccordionGroup>

## Platform Terms

<AccordionGroup>
  <Accordion title="Environment">
    Environment is the physical or logical environment where API Proxies run. Each environment has its own Gateway instances and configurations. It corresponds to the Kubernetes Namespace concept.

    For detailed information, see the [What is Environment?](/en/concepts/core-concepts/what-is-environment) page.
  </Accordion>

  <Accordion title="Project">
    Project is a logical grouping that enables API Proxies, Policies, or other definitions to be managed on a project basis.

    **Apinizer enables the creation of Projects, and API Proxies, Policies, or other definitions can be managed on a project basis.**

    For detailed information, see the [What is Project?](/en/concepts/core-concepts/what-is-project) page.
  </Accordion>

  <Accordion title="Team">
    Team is the group formed by members working on a project. It enables operations such as adding users to Projects or Role assignment to be done in bulk through Teams.

    **Apinizer allows the creation of Teams, adding Users to Teams with different Roles, assigning Teams to Projects with different roles, or assigning Roles to Teams.**
  </Accordion>

  <Accordion title="User">
    **It is the name given to stakeholders who use Apinizer interfaces. From this perspective, all stakeholders except API Consumer are Users. It should not be confused with Clients accessing API Proxies.**
  </Accordion>

  <Accordion title="Role">
    It is the name given to permission groups. **Apinizer provides certain roles as default values and allows the creation of new roles.**
  </Accordion>

  <Accordion title="Privilege">
    A user needs to have the privilege related to a specific task to be able to do that task.

    **In the Apinizer context, Privileges come pre-defined and are used for creating/updating Roles. Privileges are not directly assigned to Users.**
  </Accordion>

  <Accordion title="Namespace">
    Corresponds to the Namespace concept in the Kubernetes environment. The environment concept in the Apinizer Platform corresponds to the Namespace concept in the Kubernetes environment. Each environment is created as a Namespace in Kubernetes.
  </Accordion>

  <Accordion title="Relative Path">
    The prefix that all API Proxy relative paths in a project will start with. For example, when the project relative path is "account", the API proxy relative path appears as `/account/proxy1`.
  </Accordion>

  <Accordion title="Access URL">
    Each environment has its own access address (URL). API Proxies in the environment can be accessed through this address.
  </Accordion>
</AccordionGroup>

## Term Categories

### API Management Terms

<CardGroup cols={2}>
  <Card title="API Proxy" icon="network-wired" href="/en/concepts/core-concepts/what-is-api-proxy">
    Learn about API Proxy concept
  </Card>

  <Card title="Policy" icon="shield" href="/en/concepts/core-concepts/what-is-policy">
    Learn about Policy concept
  </Card>

  <Card title="Routing and Upstream" icon="route" href="/en/concepts/core-concepts/routing-and-upstream">
    Learn about Routing and Upstream concepts
  </Card>

  <Card title="Client Route" icon="arrow-right" href="/en/concepts/core-concepts/client-route">
    Learn about Client Route concept
  </Card>

  <Card title="Upstream Target" icon="arrow-left" href="/en/concepts/core-concepts/routing-and-upstream#upstream-target">
    Learn about Upstream Target concept
  </Card>

  <Card title="Endpoint" icon="code" href="/en/concepts/core-concepts/endpoint">
    Learn about Endpoint concept
  </Card>

  <Card title="Load Balancing" icon="route" href="/en/concepts/core-concepts/routing-and-upstream#load-balancing-strategies">
    Load Balancing strategies
  </Card>

  <Card title="Message Processing and Policy Application" icon="diagram-project" href="/en/concepts/core-concepts/message-processing-and-policy-application">
    Learn about Message Processing and Policy Application concept
  </Card>
</CardGroup>

### Platform Terms

<CardGroup cols={2}>
  <Card title="Environment" icon="layer-group" href="/en/concepts/core-concepts/what-is-environment">
    Learn about Environment concept
  </Card>

  <Card title="Project" icon="folder" href="/en/concepts/core-concepts/what-is-project">
    Learn about Project concept
  </Card>

  <Card title="Variable" icon="code" href="/en/concepts/core-concepts/variable">
    Learn about Variable concept
  </Card>

  <Card title="Environment Variable" icon="key" href="/en/concepts/core-concepts/environment-variable">
    Learn about Environment Variable concept
  </Card>

  <Card title="Connection" icon="plug" href="/en/concepts/core-concepts/connections">
    Learn about Connection concept
  </Card>

  <Card title="Connector" icon="plug" href="/en/concepts/core-concepts/connector">
    Learn about Connector concept
  </Card>

  <Card title="API Proxy Group" icon="layer-group" href="/en/concepts/core-concepts/api-proxy-group">
    Learn about API Proxy Group concept
  </Card>
</CardGroup>

### Component Terms

<CardGroup cols={2}>
  <Card title="API Manager" icon="gear" href="/en/concepts/core-components/api-manager">
    Learn about API Manager component
  </Card>

  <Card title="API Gateway" icon="shield" href="/en/concepts/core-components/api-gateway">
    Learn about API Gateway component
  </Card>

  <Card title="Identity Manager" icon="key" href="/en/concepts/core-components/identity-manager">
    Learn about Identity Manager component
  </Card>

  <Card title="Analytics Engine" icon="chart-bar" href="/en/concepts/core-components/analytics-engine">
    Learn about Analytics Engine component
  </Card>

  <Card title="API Portal" icon="globe" href="/en/concepts/core-components/api-portal">
    Learn about API Portal component
  </Card>

  <Card title="API Designer" icon="pencil" href="/en/concepts/core-components/api-designer">
    Learn about API Designer component
  </Card>

  <Card title="API Creator" icon="wand-magic-sparkles" href="/en/concepts/core-components/api-creator">
    Learn about API Creator component
  </Card>

  <Card title="API Integrator" icon="diagram-project" href="/en/concepts/core-components/api-integrator">
    Learn about API Integrator component
  </Card>

  <Card title="Cache Component" icon="memory" href="/en/concepts/core-components/cache-component">
    Learn about Cache Component
  </Card>

  <Card title="Monitoring Component" icon="eye" href="/en/concepts/core-components/monitoring-component">
    Learn about Monitoring Component
  </Card>
</CardGroup>

## Term Search and Navigation

You can search for terms in the glossary by category:

<AccordionGroup>
  <Accordion title="API Management Terms">
    * API Proxy, Policy, Routing, Endpoint
    * Client Route, Upstream Target
    * Load Balancing, Failover, Retry
    * Message Processing, Policy Pipeline
  </Accordion>

  <Accordion title="Platform Terms">
    * Environment, Project, User, Role, Privilege
    * Variable, Environment Variable
    * Connection, Connector
    * API Proxy Group, Team
    * Namespace, Relative Path, Access URL
  </Accordion>

  <Accordion title="Component Terms">
    * API Manager, API Gateway
    * Identity Manager, Analytics Engine
    * API Portal, API Designer
    * API Creator, API Integrator
    * Cache Component, Monitoring Component
    * Worker Pod, Cache Pod, Integration Pod, Service
  </Accordion>

  <Accordion title="Security Terms">
    * Authentication, Authorization
    * OAuth2, JWT, mTLS
    * IP Whitelist/Blacklist
    * Rate Limiting, Quota
  </Accordion>

  <Accordion title="Integration Terms">
    * DB-2-API, Script-2-API
    * Mock API Creator
    * Task Flow, Connector
  </Accordion>
</AccordionGroup>

## Alphabetical Term List

<AccordionGroup>
  <Accordion title="A">
    * **Access URL** - The access address (URL) belonging to each environment
    * **API** - Application Programming Interface
    * **API Gateway** - Security and management layer placed in front of APIs
    * **API Manager** - API management platform
    * **API Proxy** - The proxy of an API on the API Gateway
    * **API Proxy Group** - Management of API Proxies in groups
    * **API Consumer** - Parties using APIs
    * **API Lifecycle** - The process from API creation to deprecation
  </Accordion>

  <Accordion title="B">
    * **Connection** - Connection definitions to external systems
  </Accordion>

  <Accordion title="C">
    * **Cache Pod** - Distributed cache pods
    * **Client Route** - The point where requests from clients enter the API Proxy
    * **Connector** - Components that enable connection to different sources
  </Accordion>

  <Accordion title="D">
    * **DB-2-API** - Feature for creating APIs from database operations
  </Accordion>

  <Accordion title="E">
    * **Endpoint** - A specific URL path of an API
    * **Environment** - The environment where API Proxies run
    * **Environment Variable** - Environment-based variables
  </Accordion>

  <Accordion title="F">
    * **Failover** - Mechanism for automatically routing to a healthy backend instance
  </Accordion>

  <Accordion title="G">
    * **Gateway Engine** - The engine running the API Gateway
    * **Relative Path** - The prefix that all API Proxy relative paths in a project will start with
  </Accordion>

  <Accordion title="I">
    * **Integration Pod** - Pods where API Integrator tasks run
  </Accordion>

  <Accordion title="K">
    * **Connector** - Connection components used in API Integrator
    * **User** - Stakeholders using Apinizer interfaces
  </Accordion>

  <Accordion title="L">
    * **Load Balancing** - Load balancing strategies
  </Accordion>

  <Accordion title="M">
    * **Message Processing** - Message processing process
    * **Mock API Creator** - Feature for instantly creating Mock APIs without any server or code writing need
    * **mTLS** - Mutual TLS, mutual TLS authentication
  </Accordion>

  <Accordion title="N">
    * **Namespace** - Corresponds to the Namespace concept in the Kubernetes environment
  </Accordion>

  <Accordion title="O">
    * **Environment** - The physical or logical environment where API Proxies run
  </Accordion>

  <Accordion title="P">
    * **Policy** - Operations applied to messages in API Proxies
    * **Project** - Logical grouping of API Proxies
  </Accordion>

  <Accordion title="Q">
    * **Quota** - Limits determined for API usage
  </Accordion>

  <Accordion title="R">
    * **Rate Limiting** - Mechanism for limiting API call count
    * **Retry** - Mechanism for retrying failed requests
    * **Role** - Permission groups
    * **Routing** - Routing of requests to backend
  </Accordion>

  <Accordion title="S">
    * **Script-2-API** - Feature for creating APIs from script code
    * **Service** - Environment Service, environment service
  </Accordion>

  <Accordion title="T">
    * **Team** - The group formed by members working on a project
    * **Task Flow** - Task flows in API Integrator
  </Accordion>

  <Accordion title="U">
    * **Upstream Target** - The backend API to which requests are routed
  </Accordion>

  <Accordion title="V">
    * **Variable** - Structures that store dynamic values
  </Accordion>

  <Accordion title="W">
    * **Worker Pod** - Pods where API Proxies run
  </Accordion>

  <Accordion title="P">
    * **Privilege** - The permission required for a user to be able to do a specific task
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="Fundamental Concepts" icon="book" href="/en/concepts/core-concepts/api-proxy-group">
    Learn fundamental concepts
  </Card>

  <Card title="Fundamental Components" icon="puzzle-piece" href="/en/concepts/core-components/analytics-engine">
    Learn fundamental components
  </Card>

  <Card title="What is Apinizer?" icon="info-circle" href="/en/concepts/what-is-apinizer">
    Get information about Apinizer
  </Card>

  <Card title="Choose Your Role" icon="user" href="/">
    Review role-based guides
  </Card>
</CardGroup>