# Path Parameters and Numeric Validations { #path-parameters-and-numeric-validations }

In the same way that you can declare more validations and metadata for query parameters with `Query`, you can declare the same type of validations and metadata for path parameters with `Path`.

## Import Path { #import-path }

First, import `Path` from `fastapi`, and import `Annotated`:

{* ../../docs_src/path_params_numeric_validations/tutorial001_an_py310.py hl[1,3] *}

     *
     * @param value the numeric event type value
     */
    WitnessEventType(int value) {
        this.value = value;
    }

    /**
     * Gets the numeric event type value.
     *
     * @return the event type value
     */
    public int getValue() {
        return value;
    }

    /**
     * Gets a WitnessEventType from its numeric value.
     *
     * @param value the numeric value

    HandleType(int value) {
        this.value = value;
    }

    /**
     * Get the numeric value of this handle type
     * @return the numeric value
     */
    public int getValue() {
        return value;
    }

    /**
     * Get HandleType from numeric value
     * @param value the numeric value
     * @return the corresponding HandleType
     */
    public static HandleType fromValue(int value) {

     * If the sid cannot be resolved the numeric representation from
     * toString() is returned.
     *
     * @return display format, potentially with resolved names
     */
    String toDisplayString();

    /**
     * Return the sAMAccountName of this SID unless it could not
     * be resolved in which case the numeric RID is returned. If this

    private final int version;

    /**
     * Creates a new WitnessVersion with the specified version value.
     *
     * @param version the numeric version value
     */
    WitnessVersion(int version) {
        this.version = version;
    }

    /**
     * Gets the numeric version value.
     *
     * @return the version value
     */
    public int getValue() {
        return version;
    }

    /**

            System.clearProperty(Constants.FESS_CONFIG_PREFIX + testKey);
        }
    }

    // Test getting numeric configuration values
    public void test_get_numericValues() {
        String intKey = "numeric.int";
        String floatKey = "numeric.float";

        System.setProperty(Constants.FESS_CONFIG_PREFIX + intKey, "123");

    }

    @ParameterizedTest
    @ValueSource(strings = { "123456", "007", "999" })
    void isAllDigitsTrueForPureNumeric(String numeric) {
        assertTrue(UniAddress.isAllDigits(numeric));
    }

    @ParameterizedTest
    @ValueSource(strings = { "12a", "abc", "123 " })
    void isAllDigitsFalseForNonNumeric(String nonNumeric) {

    /**
     * Channel is being closed
     */
    CLOSING(7);

    private final int value;

    ChannelState(int value) {
        this.value = value;
    }

    /**
     * Get the numeric value of this state
     *
     * @return state value
     */
    public int getValue() {
        return value;
    }

///

## About HTTP status codes { #about-http-status-codes }

/// note

If you already know what HTTP status codes are, skip to the next section.

///

In HTTP, you send a numeric status code of 3 digits as part of the response.

These status codes have a name associated to recognize them, but the important part is the number.

In short:

            assertEquals(e.getValue(), f.get(null), e.getKey() + " value mismatch");
        }
    }

    @Test
    @DisplayName("OID values have valid dotted numeric format")
    void oidFormat() {
        assertAll(() -> assertTrue(OID_PATTERN.matcher(SpnegoConstants.SPNEGO_MECHANISM).matches(), "Invalid OID: SPNEGO_MECHANISM"),