P
Piotr Pabian
We push prospects into Snov.io lists from our own platform through the public API (POST /v1/add-prospect-to-list and /v2/prospects), including custom field values such as a personalized greeting, a personalization line and a per-recipient unsubscribe link that our email sequences use as variables.
The public API lets us read the account's custom fields (GET /v1/prospect-custom-fields) but not create them. A custom field that does not exist yet makes the request fail with "custom field not found", so every new customer account first needs someone to create 10+ fields by hand in the UI, with exact names. Until they do, contacts arrive without those values and emails go out with empty variables, which is easy to miss.
Request:
  • POST endpoint to create a prospect custom field (name, type: String/Number/Date, optional group), returning its key
  • ideally PATCH/DELETE for the same, so an integration can keep the fields in sync
  • a clear error when the 30-field limit is reached
This would let integrations set up an account fully automatically instead of asking users to click through "Manage custom fields and data tabs".