Skip to main content

Adding a duplicate recipient to an integration order

POST /v1/integration-orders/{id}/recipients now returns HTTP 200 for an exact duplicate recipient. DUPLICATE_RECIPIENT left the 422 reason-code list.

B
Written by Beau Gosse

The endpoint POST /v1/integration-orders/{id}/recipients adds one recipient to an integration order.

A duplicate recipient now returns HTTP 200. The order stays unchanged. The endpoint adds no second row. A duplicate is an exact repeat of a recipient already on the order.

Before this change the endpoint returned HTTP 422 with the reason code DUPLICATE_RECIPIENT. That reason code is no longer returned. It left the published 422 reason-code list.

What this means for your integration

You can treat a duplicate re-post as a success. Read HTTP 200 as accepted. A retry on a duplicate no longer fails.

The 422 response still rejects a recipient for these reasons:

  • ADDRESS_NOT_VALID

  • DO_NOT_MAIL

  • MISSING_MAIL_MERGE_FIELDS

  • ORDER_NOT_AVAILABLE

  • ORDER_TEMPLATE_MISSING

  • RETURN_ADDRESS_PARTIAL

  • RETURN_ADDRESS_MISSING_FIELDS

  • RETURN_NAME_PARTIAL

Did this answer your question?