Convention updates are the individual articles in the convention news system.
You must have the updates ConventionPrivilege to access this.
Convention Updates are accessed via /api/conventionupdate.
See "Object Properties" in Introduction for basic shared properties.
Complete details in ConventionUpdateProperties.
See "Related Objects" in Introduction for how to use them.
The Convention this conventionupdate belongs to.
The services used to fetch and manipulate convention updates.
Searching for updates across all conventions is no longer supported. To search on a single convention see "Relationships" in Convention.
POST /api/conventionupdate
Returns the same as a normal read.
GET /api/conventionupdate/xxx
Returns:
{
"id" : "xxx",
"name" : "Special Guest Steve Jackson",
...
}
PUT /api/conventionupdate/xxx
Returns the same as a normal read.
DELETE /api/conventionupdate/xxx
Returns:
{
"success" : 1
}
Sends a test message to the current user's account email address. This is required before sending to badge holders. This will raise an error if your convention has no defined badge types or badges.
POST /api/conventionupdate/xxx/test
Returns the same as a normal read.
Sends the update to all of the badge types selected for the update, or all badge holders if no badge types were selected. You can email an update only once. You must send a test (see above) before you can email badge holders. This will raise an error if your convention has no defined badge types or badges.
POST /api/conventionupdate/xxx/send
Returns the same as a normal read.
If a convention does not use badge types, you can post the update publicly without emailing. The posted update will appear publicly on the convention's Updates page. Posting an update does not restrict sending it later, if you add badge types later.
POST /api/conventionupdate/xxx/post
Returns the same as a normal read.