Sign in
Routing Strategies

Create Routing Strategy

Create a routing strategy. Requires a name and routing configuration at minimum. Channels and providers default to empty if omitted.

post/routing-strategies

Headers

Idempotency-Keystring

A unique key that makes this request idempotent. If Courier receives another request with the same Idempotency-Key, it returns the stored response from the first request without performing the operation again (including the original status code and any error). Use it to safely retry POST requests after network failures without risking duplicate sends. The key is scoped to this endpoint.

x-idempotency-expirationstring

How long the idempotency key remains valid, as a Unix epoch timestamp in seconds or an ISO 8601 date string. Only applies when Idempotency-Key is provided. If omitted, the key is retained for 25 hours; the maximum is 1 year.

Request body

namestring required

Human-readable name for the routing strategy.

descriptionstring nullable

Optional description of the routing strategy.

tagsstring[] nullable

Optional tags for categorization.

channelsMessageChannels
providersMessageProviders

Response

Created

idstring required

The routing strategy ID (rs_ prefix).

namestring required

Human-readable name.

descriptionstring nullable

Description of the routing strategy.

tagsstring[] nullable

Tags for categorization.

channelsMessageChannels required
providersMessageProviders required
createdinteger required

Epoch milliseconds when the strategy was created.

creatorstring required

User ID of the creator.

updatedinteger nullable

Epoch milliseconds of last update.

updaterstring nullable

User ID of the last updater.

Changes

Changed in 3 of the 55 revisions of this API.13

  • f76bed79a9132See the full diff
    • ○

      added the new optional header request parameter Idempotency-Key

      new-optional-request-parameter

    • ○

      added the new optional header request parameter x-idempotency-expiration

      new-optional-request-parameter

  • f0ac5c2fa86e10See the full diff
    • ○

      added the optional property description to the response with the 201 status

      response-optional-property-added

    • ○

      added the optional property tags to the response with the 201 status

      response-optional-property-added

    • ○

      added the optional property updated to the response with the 201 status

      response-optional-property-added

    • ○

      added the optional property updater to the response with the 201 status

      response-optional-property-added

    • ○

      added the required property channels to the response with the 201 status

      response-required-property-added

    • ○

      added the required property created to the response with the 201 status

      response-required-property-added

    • ○

      added the required property creator to the response with the 201 status

      response-required-property-added

    • ○

      added the required property name to the response with the 201 status

      response-required-property-added

    • ○

      added the required property providers to the response with the 201 status

      response-required-property-added

    • ○

      added the required property routing to the response with the 201 status

      response-required-property-added

  • b3dde93748681See the full diff
    • ○

      endpoint added

      endpoint-added