Plinqx Wildcard Parameters

Available: Base

Overview

Wildcard parameters let you build dynamic inbound endpoints by capturing variable path segments from the request URL. Instead of creating separate endpoints for each variation, you define a single pattern and extract values at runtime in your Flow.

Plinqx supports up to 20 wildcards per endpoint, numbered 0–19.

---

Wildcard format

Use numeric placeholders in the URL Topic field:

``` {0}, {1}, {2} … {19}

```

Example URL Topic:

``` customer/{0}/order/{1}

```

---

How matching works

When a request arrives, Plinqx matches the URL against your URL Topic pattern and extracts values at each wildcard position.

Example request:

``` POST /PlinqxV2/v1/services/customer/12345/order/ORD-789

```

Extracted values: - {0} = 12345 - {1} = ORD-789

Values are stored in the inbound request as key-value pairs:

Key	Value
0	12345
1	ORD-789

---

Configure wildcards

1. Open the Inbound API record.
2. In URL Topic , insert wildcards where the path is variable.
3. Save and activate the endpoint.

Example configuration:

``` customer/{0}/order/{1}

```

---

Use wildcards in Flow

Use the Get Key Value action to retrieve wildcard values.

Flow example:

``` Action: Get Key Value Inputs: - Key: “0” - Parameter List: {!InboundRequest.topicparameterList} Outputs: - Value -> customerId

```

Repeat the action for other wildcard keys as needed (for example, "1", "2").

---

Practical examples

Example 1: Customer order endpoint

URL Topic

``` customer/{0}/order/{1}

```

Incoming request

``` GET /PlinqxV2/v1/services/customer/ACC-12345/order/ORD-98765

```

Flow usage - {0} -> customerId - {1} -> orderId

Example 2: Versioned endpoint

URL Topic

``` v{0}/resource/{1}

```

Incoming request

``` PUT /PlinqxV2/v1/services/v2/resource/product-catalog

```

Flow usage - {0} -> API version - {1} -> resource name

---

Best practices

• Use descriptive patterns that reflect your business logic.
• Keep numbering sequential starting at {0}.
• Validate wildcard values in Flow before use.
• Prefer 2–4 wildcards per endpoint; use query parameters for optional data.

---

Troubleshooting

Wildcard value is empty

• Confirm the request URL matches the configured pattern.
• Verify you are using the correct key (for example, "0", "1").

Endpoint is not triggered

• Confirm the endpoint is Active.
• Ensure the HTTP method is enabled.
• Test with a simpler pattern (for example, test/{0}).

---

Summary

Item	Details
Wildcard format	{0} … {19}
Maximum wildcards	20 per endpoint
Configuration	URL Topic
Storage	InboundRequest.topicparameterList
Access in Flow	Get Key Value action