# Define custom endpoints After creating an endpoint set, you can configure new endpoint definitions that expose Foundry functions and actions. Follow the instructions below to create a new endpoint definition: 1. In the Custom Endpoints application, open the endpoint set that you want to add custom endpoints to and navigate to the **Configuration** tab. 2. Select **+ New endpoint** in the top right of the **Custom endpoints** table. This will open the **Create a custom endpoint** wizard. Newly created endpoint definitions will not be accessible until a release is created and deployed.

![the 'Configuration' tab and '+ New endpoint' option in the endpoint set interface.](../../../assets/9a8d66addb3d3b1e0401f1e21cf191cdac8a0b90df1510529067b3dd62033d59.webp)

3. In the **Create a custom endpoint** wizard, input your endpoint's name and select a backing action or function to be executed by your endpoint.

![Selecting an ontology execution type and a custom endpoint name.](../../../assets/0611a83e48005dcc3b32817c392fe13a51eb417795eed97935656d7d6da6ade9.webp)

4. After selecting a backing function or action, you will be asked to map each parameter to a newly defined endpoint parameter. The following configuration options are currently supported: * **User-defined request types:** `GET`, `POST`, `PUT`, `DELETE`, and `PATCH`. * **User-defined endpoint routes:** Host a new endpoint on your application's subdomain, allowing you to define a custom path with path parameters conforming to your organization's standards, such as `/form/{formId}/section/{sectionId}`. * **User-defined query parameters:** Define query parameters that will pass in additional information to the underlying function when specified. * **User-defined header parameters:** Provide additional headers in your request that can be handled and mapped to function inputs. * **User-defined request body:** Custom request body shape definitions for `POST`, `PUT`, `PATCH`, and `DELETE` requests. :::callout{theme="warning"} All parameters must be mapped in the custom endpoint definition, including optional parameters. Some JSON parameters can only be mapped to the endpoint's `requestBody`. ::: ![Selecting an ontology execution type and a custom endpoint name.](../../../assets/710f259c69d7f99dc607d31dcb6841ae1f7ae7a988b60239d1f23c5bec52bdca.webp)

5. After selecting a resource and configuring the request remapping, select **Create Endpoint** to save the new endpoint’s definition.

![A newly created custom endpoint definition.](../../../assets/d2e2094a5cac69bea2703a3d0c62fb11ecfc5d90ea7eaf116fe06a85856c7723.webp)