Connect a source rule to a target rule

Connect a source rule to a target rule

POST/api/v1/{team_slug}/{app_slug}/price-relay-connections
API
Management
Updated
Apr 26, 2026

management-api:POST:/api/v1/{team_slug}/{app_slug}/price-relay-connections

Connect a source rule to a target rule

API ownership

  • API family: Management API
  • Best for: Trusted back-office workflows that create, update, organize, or delete merchant-owned data.
  • Do not use from: Browser-only storefront code or public clients.
  • Guide route: /apis/management/latest

The OpenAPI contract defines the method, path, parameters, request body, and responses for this operation.

Operation

  • Method: POST
  • Path: /api/v1/\{team_slug\}/\{app_slug\}/price-relay-connections
  • Summary: Connect a source rule to a target rule
  • Description: Connect a source rule to a target rule
  • OpenAPI contract: management-api
  • Operation ID: Not documented in the OpenAPI contract.

Operation key uses API family, method, and path because this OpenAPI contract does not publish an operation ID.

Parameters2 parameters
NameInRequiredTypeDescription
app_slugpathYesstringApp slug
team_slugpathYesstringTeam slug
Request bodyDocumented body
  • Required: Yes
  • Description: connection details
  • Content: application/json (object)

Input Price Relay Connection

PropertyTypeRequiredDetails
source_rule_idstringYes-
target_rule_idstringYes-

Generated example (synthetic):

{
  "source_rule_id": "string",
  "target_rule_id": "string"
}
Responses5 statuses
StatusDescriptionContent
200connection createdapplication/json (object)
400Invalid requestapplication/json (object)
404Rule not foundapplication/json (object)
409Already connectedapplication/json (object)
500Internal server errorapplication/json (object)

200 - object

Price Relay Connection Response

PropertyTypeRequiredDetails
dataobjectYes-
detailsstring[]NoAdditional contextual information about the response. Used to provide supplementary details beyond the main data payload, such as validation warnings or processing notes
successbooleanYes-
Price Relay Connection
PropertyTypeRequiredDetails
created_atstringNo-
idstringNo-
source_rule_idstringNo-
target_rule_idstringNo-

Generated example (synthetic):

{
  "data": {
    "created_at": "string",
    "id": "string",
    "source_rule_id": "string",
    "target_rule_id": "string"
  },
  "details": [
    "string"
  ],
  "success": false
}

400 - object

Error Message

PropertyTypeRequiredDetails
detailsstring[]No-
messagestringNo-
successbooleanYes-

Generated example (synthetic):

{
  "details": [
    "string"
  ],
  "message": "string",
  "success": false
}

404 - object

Error Message

PropertyTypeRequiredDetails
detailsstring[]No-
messagestringNo-
successbooleanYes-

Generated example (synthetic):

{
  "details": [
    "string"
  ],
  "message": "string",
  "success": false
}

409 - object

Error Message

PropertyTypeRequiredDetails
detailsstring[]No-
messagestringNo-
successbooleanYes-

Generated example (synthetic):

{
  "details": [
    "string"
  ],
  "message": "string",
  "success": false
}

500 - object

Error Message

PropertyTypeRequiredDetails
detailsstring[]No-
messagestringNo-
successbooleanYes-

Generated example (synthetic):

{
  "details": [
    "string"
  ],
  "message": "string",
  "success": false
}

Contract identity

Use these fields to confirm you are implementing the intended endpoint contract.

  • API family: Management API
  • Method: POST
  • Path: /api/v1/\{team_slug\}/\{app_slug\}/price-relay-connections
  • Operation ID: Not documented in the OpenAPI contract.
  • OpenAPI tag: Price Relay Rules
  • OpenAPI summary: Connect a source rule to a target rule

Connect a source rule to a target rule

# Connect a source rule to a target rule Connect a source rule to a target rule
POST /api/v1/{team_slug}/{app_slug}/price-relay-connections
Purpose

Connect a source rule to a target rule

Required inputs

app_slug path team_slug path

Primary response

200 ยท connection created

Operation key

management-api:POST:/api/v1/{team_slug}/{app_slug}/price-relay-connections

## API ownership - API family: Management API - Best for: Trusted back-office workflows that create, update, organize, or delete merchant-owned data. - Do not use from: Browser-only storefront code or public clients. - Guide route: [/apis/management/latest](/apis/management/latest) The OpenAPI contract defines the method, path, parameters, request body, and responses for this operation. ## Operation - Method: `POST` - Path: `/api/v1/{team_slug}/{app_slug}/price-relay-connections` - Summary: Connect a source rule to a target rule - Description: Connect a source rule to a target rule - OpenAPI contract: management-api - Operation ID: Not documented in the OpenAPI contract. - Stable operation key: `management-api:POST:/api/v1/{team_slug}/{app_slug}/price-relay-connections` Operation key uses API family, method, and path because this OpenAPI contract does not publish an operation ID. ## Parameters | Name | In | Required | Type | Description | | --- | --- | --- | --- | --- | | app_slug | path | Yes | string | App slug | | team_slug | path | Yes | string | Team slug | ## Request body - Required: Yes - Description: connection details - Content: application/json (object) ### Input Price Relay Connection | Property | Type | Required | Details | | --- | --- | --- | --- | | `source_rule_id` | string | Yes | - | | `target_rule_id` | string | Yes | - | **Generated example (synthetic):** ```json { "source_rule_id": "string", "target_rule_id": "string" } ``` ## Responses | Status | Description | Content | | --- | --- | --- | | 200 | connection created | application/json (object) | | 400 | Invalid request | application/json (object) | | 404 | Rule not found | application/json (object) | | 409 | Already connected | application/json (object) | | 500 | Internal server error | application/json (object) | ### 200 - object #### Price Relay Connection Response | Property | Type | Required | Details | | --- | --- | --- | --- | | `data` | object | Yes | - | | `details` | string[] | No | Additional contextual information about the response. Used to provide supplementary details beyond the main data payload, such as validation warnings or processing notes | | `success` | boolean | Yes | - | ##### Price Relay Connection | Property | Type | Required | Details | | --- | --- | --- | --- | | `created_at` | string | No | - | | `id` | string | No | - | | `source_rule_id` | string | No | - | | `target_rule_id` | string | No | - | **Generated example (synthetic):** ```json { "data": { "created_at": "string", "id": "string", "source_rule_id": "string", "target_rule_id": "string" }, "details": [ "string" ], "success": false } ``` ### 400 - object #### Error Message | Property | Type | Required | Details | | --- | --- | --- | --- | | `details` | string[] | No | - | | `message` | string | No | - | | `success` | boolean | Yes | - | **Generated example (synthetic):** ```json { "details": [ "string" ], "message": "string", "success": false } ``` ### 404 - object #### Error Message | Property | Type | Required | Details | | --- | --- | --- | --- | | `details` | string[] | No | - | | `message` | string | No | - | | `success` | boolean | Yes | - | **Generated example (synthetic):** ```json { "details": [ "string" ], "message": "string", "success": false } ``` ### 409 - object #### Error Message | Property | Type | Required | Details | | --- | --- | --- | --- | | `details` | string[] | No | - | | `message` | string | No | - | | `success` | boolean | Yes | - | **Generated example (synthetic):** ```json { "details": [ "string" ], "message": "string", "success": false } ``` ### 500 - object #### Error Message | Property | Type | Required | Details | | --- | --- | --- | --- | | `details` | string[] | No | - | | `message` | string | No | - | | `success` | boolean | Yes | - | **Generated example (synthetic):** ```json { "details": [ "string" ], "message": "string", "success": false } ``` ## Contract identity Use these fields to confirm you are implementing the intended endpoint contract. - API family: Management API - Method: `POST` - Path: `/api/v1/{team_slug}/{app_slug}/price-relay-connections` - Operation ID: Not documented in the OpenAPI contract. - Stable operation key: `management-api:POST:/api/v1/{team_slug}/{app_slug}/price-relay-connections` - OpenAPI tag: Price Relay Rules - OpenAPI summary: Connect a source rule to a target rule