Amara API: Backwards Compatible Changes due Jan. 31st

1 view
Skip to first unread message

Darren Bridenbeck

unread,
Jan 23, 2017, 12:40:07 PM1/23/17
to API-...@amara.org

Dear Amara API users,


On January 31st, we will be making a small update to the Amara API. We don't expect these changes to affect clients, but we're notifying in advance, in the unlikely case that you experience anything unexpected.  If you believe these changes could cause issues with your use of Amara, please let us know by Friday, January 27th. Thank you!


User Activity Endpoint (backwards compatible)

The user activity endpoint will now accept all types of user identifiers, not just usernames.  Both of these URLs will now work:

  • /api/users/[username]/activity/

  • /api/users/id$[secure_id]/activity/


User Endpoint (backwards compatible)

The user endpoint will now return links to the secure_id version in the activity_uri field


Removing the "Safe team members endpoint" (/api/teams/[slug]/safe-members/)

This one isn't backwards compatible, but as far as we can tell from our logs no one is using it.  We originally announced this change for December, but we waited until now to put it into effect.  If anyone is using this endpoint, please notify us.


Best,

Darren and the rest of the Amara team

Reply all
Reply to author
Forward
0 new messages