Loops
GET /api/v1/contacts/customFields endpoint removal
Deprecated, no dateSubscribe to LoopsShare
Loops announced on January 14, 2025, that GET /api/v1/contacts/customFields is deprecated without a shutdown date. Loops deprecated the endpoint in favor of an updated replacement. Calls directed to this endpoint will eventually fail once it is fully removed.
Calls it hits
GET /api/v1/contacts/customFields
What to use instead of these calls
Use List contact properties (GET /api/v1/contacts/properties) instead.
In Loops's words
the List custom fields endpoint is now deprecated in favor of the new List contact properties endpoint.
Facts
- API
- Loops
app.loops.so - Kind
- Endpoint removal
- Announced
- January 14, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Loops's own pages
Questions
When does this change take effect?
Loops deprecated GET /api/v1/contacts/customFields without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Loops 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 Loops 1
-
No date
GET /api/v1/transactionalEndpoint 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.