PATCH /crm/v3/properties/{objectType}/{propertyName} - missing "fieldType": "phonenumber"

Developer Support APIs & Integrations
1

Hello,

using

“fieldType”: “phonenumber” get back an error:

HubSpot benutzerdefinierte Felder: https://api.hubapi.com/crm/v3/properties/company/phone BadRequest Bad Request {“status”:“error”,“message”:“Invalid input JSON on line 1, column 103: Enum type must be one of: [calculation_equation, checkbox, number, textarea, booleancheckbox, file, text, date, radio, select]”,“correlationId”:“47bca2f1-dbeb-46a2-aa5f-430f0f1ceaf4”,“category”:“VALIDATION_ERROR”}.

But it’s still possible to use this fieldType in GUI. The API missing “phonenumber” - I think it’s a bug.

2

Hey, @nina_pashinina :waving_hand: I got a similar result. The dev doc lists phonenumber as an option for field type, so does the knowledge base article.

Test using Postman:

Request

https://api.hubapi.com/crm/v3/properties/0-1

Body

{
 "name": "phone-4",
 "label": "Phone 4",
 "type": "number",
 "fieldType": "phonenumber",
 "groupName": "contactinformation",
 "hidden": false,
 "displayOrder": 0,
 "hasUniqueValue": false,
 "formField": true
}

Response

{
 "status": "error",
 "message": "Invalid input JSON on line 5, column 18: Enum type must be one of: [calculation_equation, checkbox, number, textarea, booleancheckbox, file, text, date, radio, select]",
 "correlationId": "f179bde9-db7b-4d80-aebe-ffe34ff8c5c8",
 "category": "VALIDATION_ERROR"
}

And just like you, I can create a property with this field-type in-app and return it via the API without issue.

The property phone-3 was created in-app

Request

curl --request GET \
 --url 'https://api.hubapi.com/crm/v3/properties/contacts/phone_3?archived=false' \
 --header 'authorization: Bearer YOUR_ACCESS_TOKEN'

Response

HTTP 200

{
 "updatedAt": "2023-09-08T21:11:32.722Z",
 "createdAt": "2023-09-08T21:11:32.722Z",
 "name": "phone_3",
 "label": "phone-3",
 "type": "string",
 "fieldType": "phonenumber",
 "description": "",
 "groupName": "contactinformation",
 "options": [],
 "createdUserId": "10233975",
 "updatedUserId": "10233975",
 "displayOrder": -1,
 "calculated": false,
 "externalOptions": false,
 "archived": false,
 "hasUniqueValue": false,
 "hidden": false,
 "showCurrencySymbol": false,
 "modificationMetadata": {
 "archivable": true,
 "readOnlyDefinition": false,
 "readOnlyValue": false
 },
 "formField": true
}

I’ll need to reach out to the team that owns this endpoint and clarify what the expected behaviour is. And I’ll push to get the documentation updated as well if needed.

Thanks for flagging this discrepancy. I’ll update this thread if I get any additional information.

Best,

Jaycee