Okapi Okapi

Discourse API target_usernames body parameter removal on POST /posts.json

Deprecated, no dateSubscribe to Discourse APIShare

The body parameter target_usernames on the POST /posts.json endpoint has been deprecated without a shutdown date. Calls continuing to rely on this parameter will eventually fail once it is removed. Discourse API notes that it is deprecated in favor of an alternate recipient field.


Calls it hits

  • POST /posts.json
  • body parameter target_usernames

What to use instead of these calls

Send the comma-separated recipients in target_recipients instead.

In Discourse API's words

Deprecated. Use target_recipients instead.

Discourse API, Announcement

Facts

API
Discourse API *.discourse.group
Kind
Parameter removal
Takes effect
No date given yet
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Discourse API's own pages

Questions

When does this change take effect?

Discourse API deprecated POST /posts.json, body parameter target_usernames without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: Discourse 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.

Add to GitHub

Get notifications

Subscribe to Discourse API

Hear about each breaking change Discourse API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Discourse API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.