Freshsales API
sales_account_id body parameter removal on POST /crm/sales/api/contacts
Deprecated, no dateSubscribe to Freshsales APIShare
The body parameter sales_account_id on POST /crm/sales/api/contacts is deprecated without a shutdown date. Freshsales API states that usage of this key is deprecated. Requests relying on it will eventually fail once removed.
Calls it hits
POST /crm/sales/api/contactsbody parameter sales_account_id
What to use instead of these calls
Send the contact's accounts in sales_accounts as an array of {id, is_primary} instead of sales_account_id. This update requires modifying your payload structure beyond changing an identifier.
In Freshsales API's words
Usage of this key is deprecated. Use sales_accounts key to associate accounts to a contact.
Facts
- API
- Freshsales API
*.myfreshworks.com - Kind
- Parameter removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Freshsales API's own pages
Questions
When does this change take effect?
Freshsales API deprecated POST /crm/sales/api/contacts, body parameter sales_account_id without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Freshsales API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Freshsales API 3
-
No date
POST /crm/sales/api/contactsParameter removal Deprecated, no date -
No date
PUT /crm/sales/api/contacts/{id}Parameter removal Deprecated, no date -
No date
PUT /crm/sales/api/contacts/{id}Parameter removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.