Skyone
Skyone
English
English
  • Home
  • Data
    • Getting Started
      • Create an account
      • Recover Password
      • Quick Platform Guide
      • How to test the platform for free
      • Workspace
        • Creating a new Workspace
        • Find a Workspace
        • Sending an invitation to a Workspace
        • Editing a Workspace
      • Organizations
        • Creating an Organization
        • Organization Overview
        • Organization Management
        • Organization Monitoring
      • Settings and Preferences
        • Profile
        • Notifications
        • Usage and Billing
        • Users and Permissions
    • Modules
      • Module management
        • Creating a Module
        • Importing a Module
          • IAC Files - Integration as Code
        • Editing a module
        • Module Options
      • Settings and Operations
        • Module settings
          • Connectivity: Database
          • Connectivity: Email
          • Connectivity: REST
          • Connectivity: SOAP
          • Connectivity: File
          • Connectivity: RFC
          • Connected Account Management
        • Operations
          • Importing operations into REST Modules
          • Operation Management
        • Flows Using This Module
    • Monitoring
    • API Gateway
    • Terminals & Agent
      • Agent
        • Versions supported by Agent
        • How to Update the Agent Version
        • How to back up Agent files
      • Terminals
    • Data
      • Data Stack
        • Process Control
        • Data Stack Upload
        • File Actions
        • File Jobs
        • Data Job Parameters
        • Data Store
        • Data Share Features
        • ODBC
        • How to use the Data Engine Proxy
    • Integrations
      • Integration Management
        • Create integration
        • Import Integration
        • Edit Integration
        • Integration Options
        • Flows of this integration
      • Flows
        • Flow management
          • Creating a flow
          • Flow options
          • Flow Canva: configuring and editing the flow
            • Flow Canva: overview
            • Exception Handler
              • Exception Handler - Configuration
              • Exception Handler - Cases
            • Multicontext Flows
              • Example: Multicontext with an API Gateway
              • Example: Multicontext with a Time Trigger
            • Flow Settings
        • Triggers of a flow
          • API Gateway Triggers: Adding and Setting
          • AS2 Triggers: Adding and Setting
          • Queue Triggers: Adding and Setting
          • Flow Triggers: Adding and Setting
          • Time Triggers: Adding and Setting
          • Webhook Triggers: Adding and Setting
        • Tool Modules
          • AS2 Module
          • CSV Module
          • Data Transform Module
          • Data Balancer Module
          • EDI Module
          • Flow Call Module
          • IF Module
          • JavaScript Module
          • Log Module
          • Loop Do While Module
          • Loop For Module
          • Return Module
          • XML Module
          • Other Tool Modules
        • Module Header
        • Connecting components of a flow
        • Editing triggers and modules
        • Data Operations
          • Object Handling
            • Practical example: Handling variables
          • SMOP (Small Operations)
          • Parameterization rules
    • How to
      • Insert JSON into databases
      • Flattening: Data transformation using JSONata
      • How to use Form Data
      • Understanding recursion in JSONata
      • REST Module Output Consolidation
      • Isolated in execution: concept and application in variables
      • URL Parameters in API Gateway
      • Use case: API Gateway trigger parameters
      • Use case: Exception Handler in financial transactions
      • Use case: using Groups to manage access to flows
      • How to create a download endpoint and integrate with Power BI
      • Is it possible to use two triggers in a single flow?
      • How to set up WhatsApp in Skyone Studio
    • FAQ
    • GIGS: The complete guide
    • Glossary
  • Support
    • How do I request support?
    • Case Severity Levels
    • SLAs
    • Help & Resources
Powered by GitBook
On this page
  • Definitions
  • Create an API Gateway
  • How to edit an API Gateway
  • Version
  • Routes
  • Users
  1. Data

API Gateway

PreviousMonitoringNextTerminals & Agent

Last updated 6 months ago

Definitions

An API Gateway is an API management tool that allows you to create or use third-party APIs in one place, making it a quick and practical API management solution. It acts as a reverse proxy to accept all API calls, aggregate the various services needed to execute them, and return the appropriate result.

With this in mind, to facilitate the creation of your flows in different integrations, the platform's API Gateway solution was designed to be your API management hub, featuring Basic authentication (with username and password) for one or more users and routing (route creation). Additionally, you can not only manage external APIs but also create an API from scratch, allowing you to use it within a flow on the platform.

Create an API Gateway

You can create one or more API Gateways to control different APIs, whether they are external or created within the platform. To do this, follow these steps:

  1. In the API Gateway tab, click on "Create API Gateway".

  2. In the modal, enter the API Gateway Name, Description (Optional), choose a Group (default is "default"), and Image (Optional).

The image must be 80x80 in png, jpg or jpeg format. If no image is chosen, the API Gateway will be represented by a standard platform thumbnail, which can be changed later.

  1. To finish, click on "Create".

How to edit an API Gateway

To edit the API Gateway, simply click on the desired item. You will then be directed to the editing screen. We have separated the editing steps below:

Name and Description:

  1. To edit the "Name" and "Description", just one click will make the area editable.

  2. After making your changes, click outside the editing area or press the Enter key to save your changes.

Image

  1. To change the image, move the mouse closer and click on "Edit".

  2. Once the change has been made, click "Save".

Copying an API Gateway

To copy an API Gateway, simply click on "Copy URL".

Deleting an API Gateway

  1. To delete an API Gateway, simply click on "Delete", located in the three dots in the API Gateway editing area.

  2. Enter the name to confirm the deletion and click "Delete" to finish the action.

You can't undo the deletion.

Version

With this feature, you can create different versions for the same API, which can contain different routes and access permissions.

Creating a Version

To create a version:

  1. In "API Gateway", click on the desired item.

  2. Click on "New version".

  1. Enter the Name of the API Gateway version and click "Next Step".

  1. Create a new route (more information below) and click "Save changes".

Editing a Version

To edit a version:

  1. Under "API Gateway", click on the desired item.

  2. Under "Versions", choose the version you want to modify and click "Edit".

  3. To finish, click on "Save changes".

Deleting a Version

To delete a version:

  1. In "API Gateway", click on the desired item.

  2. Under "Versions, choose the version you want to delete and click "Delete".

  3. In the modal, enter the name to confirm the deletion and click "Delete" to finalize the action.

Routes

Now that you’ve created at least one version, you can set up one or more routes for your API.

A route is an address (URL) that directs to a flow, acting as an endpoint for accessing your API in Skyone Data. For example, you can create a route named "/products" to handle all flows related to products (saving, listing, deleting products) using one or more versions. By using routes with different HTTP methods, Skyone Data's API Gateway simplifies the use of APIs or the creation of APIs to perform various tasks in different flows.

For greater flexibility, our API Gateway allows the creation of two types of routes: Trigger and HTTP, which we’ll explore in detail below.

HTTP Route

When you create an HTTP route, which always uses an external API, you can point to a route in a given language, even if the endpoint is in a different language, making it easy for any Skyone Data user to use external APIs. So if, for example, you want to make a request to the "/orders/approve" endpoint of an API, you can create a route called "/orders/approve".

In other words, instead of using the external API, without customization, you use it with a unique URL and custom data: route, version and user access (Basic authentication).

Create an HTTP route:

  1. With the version already created, when you click on "Next steps", you will be directed to create the route.

  2. Click on "Create new route".

  1. Enter the route data:

  • Enter the Route URL you want to use in the route, which may be different from the original.

  • Choose one or more API Gateway route methods (GET, POST, PUT, PATCH OR DELETE);

  • Under Route Type, choose HTTP;

  • Enter the Protocol (HTTP or HTTPS), the Host (API address) and the Port used;

  • Enter the API's original Path (endpoint)

  • Choose the Execution limit (number of executions and period);

  • Optionally, if you have already created a user, click on the "Protected route" option and choose the user who needs access to this route;

4. To finish the action, click on "Save route".

Trigger route

When you create a Trigger route, which doesn't use an external API, you can carry out different operations without having to repeat the configuration in each flow, as well as controlling access according to the user registered in the API Gateway, if you want access to be restricted.

In other words, instead of repeating the data in different flows, you use it with a single URL and personalized data: route, version and access per user (Basic authentication).

Create a trigger route:

  1. With the version already created, by clicking on "Next steps", you will be directed to create the route.

  2. Click on "Create new route".

  3. Enter the route data:

  • Enter the Route URL you want to use in the route, which may be different from the original.

  • Choose one or more API Gateway route methods (GET, POST, PUT, PATCH OR DELETE);

  • Under Route Type, choose Trigger;

  • Choose the Execution limit (number of executions and period);

  • Optionally, if you have already created a user, click on the Protected route option and choose the user who needs access to this route;

  1. To finish the action, click on "Save route".

Edit Routes

To edit a created route at any time:

  1. Within the version of your API Gateway, choose the item you want to change and click "Edit".

  2. Once you've made your changes, click "Save changes".

Execution limit

You can manage the number of executions of your API Gateway through the Execution Limit, i.e. determining the maximum number of times the API will be requested over a period of time.

To do this, when editing a route, choose the desired number and time measure (second, minute or hour).

Finally, click on "Save changes".

The default run limit is 10 runs per minute.

Time is measured in seconds, minutes and full standard time. For example: Imagine you have a route and the limit on executions is set to 2 per minute. Even if the call starts at 08:45:55, the limit is until 08:45:59, because 08:46:00 will be counted as a new series of executions.

Delete routes

To delete a created route at any time:

  1. Within the version of your API Gateway, choose the item you want to change and click "Delete".

  2. In the modal, enter the name to confirm the deletion and click "Delete" to finalize the action.

Users

If you want to restrict access to one or more users, you can do so using an authentication (Basic ou oAuth2)

Create Users

  1. To create a user, in API Gateway, click on the Users tab.

  2. Click on "Add user";

  3. Customize the rest of the User name;

  4. Choose the authentication type: Basic or oAuth2, and follow the setup according to the selected type.

To complete the setup for a Basic user, enter the Password, then click "Save user".

To complete the setup for an oAuth2 user, click "Save user".

After creating the user, the screen will display the Client ID and Client Secret. Copy this information and enter it in the endpoint to generate the access_token.

The created users are listed under the "Users" tab in the API Gateway.

Edit Users

To edit a user:

  1. In API Gateway, in the Users tab, click on "Edit" for the desired user.

  1. Make the necessary changes and click on "Save changes".

Deleting Users

To delete a user:

  1. In API Gateway, in the Users tab, click on "Delete" for the desired user.

  2. In the modal, enter the name to confirm the deletion and click on "Delete" to finalize the action.

You can delete any user, as long as they are not currently associated with a route. If this is the case, you need to edit the routes that include the user and remove them from the "Is this route protected?".

Read also:

URL Parameters in API Gateway
Mouse pointer in the image shows the edit option