Changelog

Support for JWT authentication has been added to the following User Preference REST API endpoints:

• PUT | PATCH | DELETE /users/:user_id/preferences/:topic_id
• GET /users/:user_id/preferences
• GET /users/:user_id/preferences/:topic_id

Docs: https://www.courier.com/docs/reference/auth/issue-token/#usage

Preferences can now be associated with a tenant. If you send to a user in the context of their tenant, the preferences being applied will be the tenant level preferences, and if its not in the context of a tenant, its picked from user level preferences.

Note, this change does not impact you unless you’re using tenants. See the Tenants API reference for more information.

Automations templates can now infer recipient userId in most cases without manual configuration. User Id is inferred when:

• An automation is triggered by a CDP (Segment, Rudderstack, Courier)
• The User id is supplied in the data payload (as user_id or userId) on invoke.
• The recipient field is set on invoke

The hosted user preference age now uses brands from the tenant when a notification is sent using tenant_id.

Create a tenant using API and attach a brand_id:

1
name: "ACME Inc",
2
  brand_id: "acme_brand_new",
3
  properties: {
4
    ceo: "Person",
5
  }
6
}

When you send a notification using the above tenant, the host user preference page links generated by Courier will have appropriate acme_brand_new instead of default brand.

The syntax for sending with a tenant has been updated to improve distinction vs sending to all members of a tenant with the addition of the context property.

Please see the tenants section of users for examples of this syntax and usage.