URL field and the schemas API

I’m encountering an issue with the URL field and the API.
I created a URL field for Contacts via the UI:

I’m trying to retrieve the Contacts schema using /crm-object-schemas/v3/schemas/0-1, but I’m getting the following response:

{ "updatedAt": "2025-06-25T14:48:22.563Z", "createdAt": "2025-06-25T14:48:22.563Z", "name": "custom_url", "label": "custom_url", "type": "string", "fieldType": "text", "description": "", "groupName": "contactinformation", "options": [], "createdUserId": "7055693", "updatedUserId": "7055693", "displayOrder": -1, "calculated": false, "externalOptions": false, "archived": false, "hasUniqueValue": false, "hidden": false, "modificationMetadata": { "archivable": true, "readOnlyDefinition": false, "readOnlyValue": false }, "formField": false, "dataSensitivity": "non_sensitive"}

This field behaves like a regular “Single-line Text” field in the API response.
How can I distinguish between a “URL” field and a standard “Single-line Text” field using the API?

@Sachavskyi - There is no HubSpot property type that is specific to storage of a URL string. You are as close as it comes to defining the right property for this purpose.

Hope this is helpful.

Steve

@SteveHTM There must be because they’ve added URL property on the UI in beta: https://community.hubspot.com/t5/HubSpot-Ideas/Custom-property-of-type-URL/idc-p/1169164.
And they forgot to add this to the API.

@Sachavskyi - thanks for pointing that out! It’s hard to keep up with these sly updates not refreenced in Developer news or elsewhere unless you are lucky!
Reaction to the implementation Beta seems distinctly mixed - you would expect that a Beta was intended to gather feedback to improve things before general release. Product management seems to have forgotten that convention here.

Steve