API Nodes

API Nodes allow you to turn any custom Atlas workflow into a callable API endpoint directly integrated into Unity, Unreal Engine and/or custom engines

API Nodes

API Nodes allow you to turn any custom Atlas workflow into a callable API endpoint. They define how data enters and leaves a graph when exporting an API via the API From Graph feature.

Use these nodes whenever you want to:

• Deploy a workflow as a REST API

• Trigger Atlas processes programmatically

• Integrate Atlas with external tools (Unity, Blender, n8n, Flask, Unreal Engine, etc.)

Overview

There are two categories of API Nodes:

1. Input API Nodes — define what data your external request can send into the workflow.

2. Output API Nodes — define what the workflow returns after execution.

Once these nodes are placed, the workflow can be exported as an API directly from the toolbar.

Input API Nodes

Input API Nodes replace native inputs so that external applications can provide data through the API.

Available Input Types

• API Input Text – accepts string data

• API Input Number– accepts numeric values

• API Input Boolean– accepts true/false flags

• API Input Image – accepts image file uploads

• API Input Mesh – accepts mesh files (GLB, OBJ)

Use these nodes when preparing your graph for external execution.

Output API Nodes

API Output Nodes define what the API returns when the workflow completes.

Available Output Types

• API Output Text– returns text strings

• API Output Number– returns numeric values

• API Output Boolean– returns true/false results

• API Output Image – returns generated images

• API Output Mesh– returns mesh files

• API Output SVG – returns vector graphics

Replace the final node’s output with the corresponding API Output Node to expose your result.

Exporting Your Custom Workflow as an API

After setting the inputs and outputs with API Nodes, you can export your workflow as an API:

Steps

1. Build your workflow as usual.

2. Replace all required inputs in your workflow with the corresponding Input API Nodes.

3. Add an Output API Node and connect it to your final output node to expose the result through the API.

4. Click the Export API icon in the toolbar.

5. Enter a name for your API.

6. Click Create.

The platform then generates:

• Bash example

• Python example

• Full API JSON specification

• Your API ID

These can be used immediately to call your workflow programmatically.

Using the Generated API

Once created, the API can be called from any environment:

• Python scripts

• Bash / curl

• Web backends

• Unity or Unreal Engine tools

• n8n or automation pipelines

• Blender scripts

• Custom UIs

Your API ID ensures that the workflow is executed with the exact graph and nodes you configured.