# URL
## Introduction
The endpoint **URL** page is used to define the HTTP method and URL to be used, and any required URL parameters:
## Endpoint URL
To add an endpoint URL, you must select the appropriate HTTP method:
...and then add the required URL:
## Endpoint parameters
You can define two types of parameter:
* [Required](#required-parameters) parameters are added as key pairs and are always applied for the endpoint, whenever it is used. Use the top panel to add required parameters.
* [Optional](#optional-parameters) parameters are displayed as [connection shape](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/building-process-flows/process-flow-shapes/standard-shapes/connector-shape) filters, so users can apply with their own values when using this endpoint as a data source in [process flows](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/about-process-flows). Use the lower panel to add optional parameters.
Any parameters that you add (to either panel) here are **automatically** appended to the existing [endpoint URL](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/developer-hub/connector-builder/building-your-own-connector/4-endpoints/..#configuring-an-endpoint) as a query parameter when this endpoint is used in [process flows](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/about-process-flows).
## Required parameters
If you have parameters that must always be passed in the **endpoint request URL**, add them to the top panel. Default parameters are added as key pairs, and are passed straight into requests - users are never asked to provide values for these in [process flows](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/about-process-flows).
In the example below, our endpoint URL is set to GET all products, but we are adding a default URL parameter to add a query which will only retrieve products with a `product_type` of `snowboard`:
By adding this as a **default URL parameter** for the endpoint, this query will be applied whenever this endpoint is added to [process flows](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/about-process-flows) (via a [connection shape](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/building-process-flows/process-flow-shapes/standard-shapes/connector-shape)). The actual endpoint used will be:
```
https://parseapi.back4app.com/classes/product?product_type=snowboards
```
{% hint style="info" %}
You can define static values for a default URL parameter, or use a variable. For an example of where variables might be useful here, see [What if I want to force users to enter their required value for a URL parameter?](#what-if-i-want-to-force-users-to-enter-their-required-value-for-a-url-parameter)
{% endhint %}
## Optional parameters
Optional parameters are available for your users to update with their own required values, in process flows.
If we consider the example above - we are always restricting our 'GET all products' endpoint to return only products with a `product_type` of `snowboard`. But suppose we wanted to allow users to choose a `product_type` at the point they are running a process flow?
When a [process flow](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/about-process-flows) includes a [connection shape](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/building-process-flows/process-flow-shapes/standard-shapes/connector-shape) which is configured to use this endpoint, users can see/update filter fields for any **optional URL parameters** that have been defined for the endpoint. For example, let's add an optional parameter for `product_type`:
What does the 'use as default' option do?
If you toggle ON the `use as default option`, this parameter will be displayed for users to see/update when they first access the saved connection shape - for example:
If this option is OFF, users won't see it unless they select the add new filter button and add it manually - for example:\
\
Now if we configure a [process flow connection shape](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/building-process-flows/process-flow-shapes/standard-shapes/connector-shape) with this endpoint, a **product\_type** filter option is available, so the person running this flow can choose to use it if they wish:
When a process flow runs for this connector, associated API requests are injected with the user-provided URL parameter value wherever a `{{product_type}}` parameter is found.
{% hint style="info" %}
These are optional parameters - users are not required to provide a value for the associated connection shape in process flows.
{% endhint %}
## What if I want to force users to enter their required value for a URL parameter?
[Optional URL parameters](#optional-parameters) are just that - [process flow](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/about-process-flows) users can choose to add a parameter value if they wish. If a user doesn't choose to update an optional URL parameter field, then no query is applied.
However, there may be scenarios where you need to ensure that a URL parameter is always provided by users running a process flow. For this, a slightly different approach is needed - in this case, you would:
**Step 1**\
Add a 'required' [endpoint variable](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/developer-hub/connector-builder/building-your-own-connector/4-endpoints/endpoint-options/endpoint-variables) for the field that you want to force users to update in process flows.
Show me
**Step 2**\
Update the [endpoint URL](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/developer-hub/connector-builder/building-your-own-connector/4-endpoints/..#configuring-an-endpoint) to include a query for this variable.
Show me
**Step 3**\
Add a [default URL parameter](#default-parameters), specifying your endpoint variable (added in step 1) as the parameter value.
Show me
**Step 4**\
Now when a user adds this endpoint to a [connection shape](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/building-process-flows/process-flow-shapes/standard-shapes/connector-shape) in a [process flow](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/about-process-flows), they must update this variable field before proceeding.
Show me
## More information
Techniques for adding **URL parameters** are same as all other types of parameters that you may encounter in the connector builder. For information about these options please see the [Working with parameters](https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/developer-hub/connector-builder/building-your-own-connector/techniques-for-working-with-variables-and-parameters/working-with-parameters) page.
What does the 'use as default' option do?
Show me