How to define a new origin for your application

This guide explains how to configure an origin. An origin, also known as a backend, is the server from which Azion retrieves your content. Origins can include object storage services, cloud servers, or other infrastructure that hosts your application assets or data.

There are separate instructions for API v3 using legacy Origin settings and API v4 using the new Connector product.

Access Azion Console > Connector.
Click the + Connector button.
In the General section, give your connector a unique and descriptive name (My Object Storage Connector).
In the Connector Type section, select HTTP.

In the Connection Options section, locate the Transport Protocol Policy field and select Force HTTPS.
In the Address Management section, locate the Address field and add httpbin.org.
Under Host, add customhost.com.
Click the Save button.

To activate the Connector in your application:

Access the Rules Engine tab.
Edit the default rule or add a new request rule.
Give a name for your rule.
Select Request Phase.
Under the Criteria section, select the variable ${uri}.
As a comparison operator, select is equal.
As an argument, add /httpbin.
In the Behaviors section, select Set Connector from the behavior list.
Select the new Connector you created.
Click the Save button.
Wait a few minutes for the changes to propagate and access xxxxxxxxxx.map.azionedge.net/httpbin.

When you create an application, a default origin is created and activated automatically. This guide will show you how to create and activate a new origin with different configurations without removing or editing the default origin.

Access Azion Console > Applications.
Click the application for which you want to configure a new origin.
Select the Origins tab.
Click the + Origin button.
Give your new origin a name. For example: httpbin.org
Under Type, keep the option Single Origin selected.

Under Protocol Policy, select Enforce HTTPS.
Under Address, add httpbin.org
Under Host Header, add customhost.com.
Leave Path blank.
Click the Save button.

You’ve created a new origin, but it isn’t active in your application yet. You need to define what will trigger a request to the new origin.

Navigate to the Rules Engine tab.
Click the + Rule button.
Give a name for your rule.
Select Request Phase.
Under the Criteria section, select the variable ${uri}.

As a comparison operator, select is equal.
As an argument, add /httpbin.
In the Behaviors section, select Set Origin from the behavior list.
Select the new origin you created.
Click the Save button.
Wait a few minutes for the changes to propagate and access xxxxxxxxxx.map.azionedge.net/httpbin.

Run the following POST request in your terminal, replacing [TOKEN VALUE] with your personal token and the <application_id> variable with your application ID:

curl --location 'https://api.azionapi.net/edge_applications/<application_id>/origins' --header 'Accept: application/json; version=3' --header 'Content-Type: application/json' --header 'Authorization: Token [TOKEN VALUE]' --data '{
      "name": "httpbin.org SO HTTPS Host:customhost.com",
      "origin_type": "single_origin",
      "addresses": [
          {
              "address": "httpbin.org"
          }
      ],
      "origin_protocol_policy": "https",
      "host_header": "customhost.com"
}'

Key	Description
`name`	Sets the string in value as a name of the origin.
`origin_type`	Sets the new origin type to `single_origin`. For more information on load balancing, check Work with multiple origins.
`addresses`	Takes a list of objects for each address of the origin. Since this is an entry of the single origin type, you may only send one object with the `address` value in the array.
`origin_protocol_policy`	When `https`, enforces an HTTPS connection with the origin, not affecting the protocol from user requests.
`host_header`	Sets the string in value as the value of the `Host` header sent to the origin.

You’ll receive a response similar to this:

{
  "results": {
      "origin_id": <origin_id>,
      "origin_key": <origin_key>,
      "name": "httpbin.org SO HTTPS Host:customhost.com",
      "origin_type": "single_origin",
      "addresses": [
          {
              "address": "httpbin.org",
              "weight": null,
              "server_role": "primary",
              "is_active": true
          }
      ],
      "origin_protocol_policy": "https",
      "is_origin_redirection_enabled": false,
      "host_header": "customhost.com",
      "method": "",
      "origin_path": "",
      "connection_timeout": 60,
      "timeout_between_bytes": 120,
      "hmac_authentication": false,
      "hmac_region_name": "",
      "hmac_access_key": "",
      "hmac_secret_key": ""
  }
}

Run the following POST request in your terminal, replacing [TOKEN VALUE] with your personal token, the <application_id> variable with your application ID, and the <origin_id> variable with the origin ID from when you created a new origin via API:

curl --location 'https://api.azionapi.net/edge_applications/<application_id>/rules_engine/request/rules' --header 'Accept: application/json; version=3' --header 'Content-Type: application/json' --header 'Authorization: Token [TOKEN VALUE]' --data '{
  "name": "Set httpbin /httpbin",
  "behaviors": [
      {
          "name": "set_origin",
          "target": "<origin_id>"
      }
  ],
  "criteria": [
      [
          {
              "variable": "${uri}",
              "operator": "is_equal",
              "conditional": "if",
              "input_value": "/httpbin"
          }
      ]
  ]
}'

You’ll receive a response confirming that the rule was created.
Wait a few minutes for the changes to propagate and access xxxxxxxxxx.map.azionedge.net/httpbin. Also, try accessing any other unconfigured URI: you should receive a 404 error.

Run the following POST request in your terminal, replacing [TOKEN VALUE] with your personal token and the <application_id> variable with your application ID:

curl --request POST --url https://api.azion.com/v4/edge_connector/connectors --header 'Accept: application/json' --header 'Authorization: Token [TOKEN VALUE]' --header 'Content-Type: application/json' --data '{
  "name": "httpbin.org SO HTTPS Host:customhost.com",
  "active": true,
  "type": "http",
  "attributes": {
    "addresses": [
      {
        "active": true,
        "address": "httpbin.org",
        "http_port": 80,
        "https_port": 443
      }
    ],
    "connection_options": {
      "dns_resolution": "preserve",
      "transport_policy": "force_https",
      "http_version_policy": "http1_1",
      "host": "customhost.com",
      "path_prefix": "",
      "following_redirect": false,
      "real_ip_header": "X-Real-IP",
      "real_port_header": "X-Real-PORT"
    },
    "modules": {
      "load_balancer": {
        "enabled": false,
        "config": {
          "method": "round_robin",
          "max_retries": 0,
          "connection_timeout": 60,
          "read_write_timeout": 120
        }
      },
      "origin_shield": {
        "enabled": false,
        "config": null
      }
    }
  }
}'

Key	Description
`name`	Sets the string in value as a name of the origin.
`type`	Sets the new Connector type to `http`. For more information on load balancing, check Work with multiple origins.
`addresses`	Takes a list of objects for each address of the origin. Since this is an entry of the single origin type, you may only send one object with the `address` value in the array.
`transport_policy`	When `https`, enforces an HTTPS connection with the origin, not affecting the protocol from user requests.
`host`	Sets the string in value as the value of the `Host` header sent to the origin.

You’ll receive a response similar to this:

{

{
"state": "pending",
"data": {
  "id": <connector_id>,
  "name": "httpbin.org SO HTTPS Host:customhost.com",
  "last_editor": "your-email@example.com",
  "last_modified": "2025-08-14T18:12:20.161667Z",
  "active": true,
  "product_version": "1.0",
  "type": "http",
  "attributes": {
    "addresses": [
      {
        "active": true,
        "address": "httpbin.org",
        "http_port": 80,
        "https_port": 443,
        "modules": null
      }
    ],
    "connection_options": {
      "dns_resolution": "preserve",
      "transport_policy": "force_https",
      "http_version_policy": "http1_1",
      "host": "customhost.com",
      "path_prefix": "",
      "following_redirect": false,
      "real_ip_header": "X-Real-IP",
      "real_port_header": "X-Real-PORT"
    },
    "modules": {
      "load_balancer": {
        "enabled": false,
        "config": null
      },
      "origin_shield": {
        "enabled": false,
        "config": null
      }
    }
  }
}
}

Run the following POST request in your terminal to bind the new Connector to your Applications replacing [TOKEN VALUE] with your personal token, the <application_id> variable with your application ID, and the <connector_id> variable with the Connector ID from the previous step:

curl --request POST --url https://api.azion.com/v4/edge_application/applications/<application_id>/request_rules --header 'Accept: application/json' --header 'Authorization: Token [TOKEN VALUE]' --header 'Content-Type: application/json' --data '{
"name": "string",
"active": true,
"criteria":
  [
    {
      "conditional": "if",
      "variable": "${uri}",
      "operator": "is_equal",
      "argument": "/httpbin"
    }
  ]
],
"behaviors": [
  {
    "type": "set_edge_connector",
    "attributes": {
      "value": "<connector_id>"
    }
  }
]
}'

You’ll receive a response confirming that the rule was created.
Wait a few minutes for the changes to propagate and access xxxxxxxxxx.map.azionedge.net/httpbin. Also, try accessing any other unconfigured URI and you should receive a 404 error.