Loops
GET /api/v1/transactional endpoint removal
Deprecated, no dateSubscribe to LoopsShare
Loops has deprecated the GET /api/v1/transactional endpoint without announcing a shutdown date. Calls made to this route are slated to fail. The change directly affects any integration querying the GET /api/v1/transactional endpoint.
Calls it hits
GET /api/v1/transactional
What to use instead of these calls
Use the new List transactional emails endpoint instead.
In Loops's words
This endpoint is deprecated. Use List transactional emails instead.
Facts
- API
- Loops
app.loops.so - Kind
- Endpoint removal
- 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/transactional 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/contacts/customFieldsEndpoint 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.