Skip to main content


Build API Endpoints

An API endpoint provides the actual business logic and data for your API. You need to develope and deploy APIs before integrating them with API7 Enterprise.

Develop API Endpoints

This section lists workflow to develop an API endpoint.

  1. Scheduling: Scheduling is a key aspect of the API development process. People in your team should complete and report their work based on the scheduled timeline to ensure delivering the project timely.
  2. Development and Self-Testing: Typically, development involves coding and debugging, while self-testing involves testing and validating developed APIs to ensure their functionality.
  3. Integration Testing: Integration testing is a stage where APIs between different modules are debugged and tested to ensure correct and stable interactions and communications.
  4. QA Testing: QA testing (or quality assurance testing) aims to identify and eliminate defects or vulnerabilities in an API before it is released. It is critical for the API reliability and security.
  5. Product Acceptance: Product acceptance involves comprehensive testing, evaluation, and confirmation to determine whether an API meets the expected goals and standards. This stage is vital for ensuring that the API is ready for production and meets your' requirements.
  6. Deployment: Once the API has passed all necessary tests and evaluations, it will be deployed to the production environment. Then, you can access and utilize the API.

Deploy API Backend

When deploying an API backend, you should consider API scalability, availability, portability, and son on.

  • Virtual machines: Deploy service binaries/packages on VMs directly.
  • Containers: Package services as Docker containers and deploy on orchestrators like Kubernetes.
  • Serverless: Develop functions and deploy on platforms like AWS Lambda.
  • On-premise: Host services on existing on-premise infrastructure.

Define API Endpoints

Once deployed, the API backend must be configured with network endpoints that the API7 Enterprise can route requests to.

  • Virtual Machines: Assign public IP addresses and open ports on VM firewalls for service endpoints.
  • Containers: Use Kubernetes Ingress or LoadBalancer services to expose endpoints.
  • Serverless: Most serverless platforms automatically assign invoked URLs for functions.
  • On-premise: Define URLs or IP addresses with ports for on-premise services, and the allowlist of IP addresses of API7 Enterprise.

Detect API Backends

You can use either of the following way to detect API backends:

  • Implement Health Checks (Highly Recommended)

    Configure health check endpoints for backend services to allow API7 Enterprise to detect availability and route traffic accordingly.

  • Use Service Discovery (Optional)

    Service discovery mechanisms, such as Consul, Eureka, Nacos or Kubernetes Service Discovery, can be used to dynamically detect backend nodes. Logo

API Management for Modern Architectures with Edge, API Gateway, Kubernetes, and Service Mesh.


API7 Cloud

SOC2 Type IRed Herring

Copyright © APISEVEN Ltd. 2019 – 2024. Apache, Apache APISIX, APISIX, and associated open source project names are trademarks of the

Apache Software Foundation