/api/templates* → endpoint removal
Airship API
Deprecated, no date
Airship deprecated the Personalization API for /api/templates* without a shutdown date. Calls made to these endpoints will eventually fail. The change impacts all callers using personalization templates directly through this API.
Calls it hits
/api/templates*
What to use instead of these calls
Create templates in the Airship dashboard or with the Content API, and send with the Bulk sending or Automation APIs instead of /api/templates/push and /api/templates/schedules. This migration requires deciding where templates are kept and how they are sent rather than simply updating an identifier.
Templates leave the API for the dashboard or the Content API: where they are kept and how they are sent is the team's call.
In Airship API's words
The Personalization ( /templates ) API is deprecated. Instead, create templates in the Airship dashboard or use the Content API , and send using the Bulk sending or Automation APIs.
Facts
- API
- Airship API
go.urbanairship.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Airship API's own pages
Questions
When does this change take effect?
Airship API deprecated /api/templates* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Airship 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.