uncategorized
curiouspencil at December 18th, 2024 10:05 — #1
I am setting up a few Make.com API requests and I need to find all of my custom field IDs. I have looked on another forum and it suggested use a GET request with the following URL: https://app.onepagecrm.com/api/v3/custom_fields.json
However this only returns one custom field ID and it is not the one I want to use.
Any help with this would be greatly appreciated.
Thanks in advance
sajedalmorsy at December 19th, 2024 10:49 — #2
Hi @Curiouspencil
Custom fields in OnePageCRM are organized into three categories: Contacts, Companies, and Deals. Below are the endpoints to retrieve custom fields for each category:
Contacts:
https://app.onepagecrm.com/api/v3/custom_fields
Companies:
https://app.onepagecrm.com/api/v3/company_fields
Deals:
https://app.onepagecrm.com/api/v3/deal_fields
I hope this information is helpful! Please don’t hesitate to reach out if you have any further questions.
Best regards,
Sajed
OnePageCRM
vladimir at December 19th, 2024 15:00 — #3
Hello Curiouspensil!
Our API gives you all the contacts' custom fields it has, you can manage the number of custom fields in the output using per_page
parameter (by default it is 10) and page
parameter for getting the necessary (or just the next) page, they start with 1, so in order to get the 2nd page you should pass page=2
in your request. You can also order the output with order
and sort_by
params (see our docs https://developer.onepagecrm.com/api/#/Contacts/get_contacts for details)
Also our API exposes you deals' custom fields and companies' custom fields in the following endpoints (respectively)
1. https://app.onepagecrm.com/api/v3/deal_fields.json
2. https://app.onepagecrm.com/api/v3/company_fields.json
If you need some assistance please provide some details on your case, like request, params, etc.
Please contact us if you have questions on the usage or experience any issues using our API.
Thank you,
Vladimir
curiouspencil at December 31st, 2024 06:26 — #4
Thank you that has been helpful
Powered by Discourse, best viewed with JavaScript enabled