You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Document service_request_number placement on mailpieces (#538)
Adds a shared service_request_number attribute and references it from the
postcard, letter, self mailer, and check create models (the four resources
that accept it per lob-api validators). The field was previously undocumented,
which led a customer to nest it inside merge_variables where the API silently
ignores it — the mailpiece is created with no promotion applied and no error.
The description states the field must be top-level and must not be nested in
merge_variables, and the postcard create examples now include it as a sibling
of size. Mirrors the USPS promotions help-center language.
Follow-up to ER-515.
The service request number (SR#) of an approved USPS promotion (for example, the Integrated Technology promotion) to apply to this mailpiece. Supported on letters, postcards, self mailers, and checks.
18506
+
18507
+
This must be a **top-level** field in the create request, alongside `size`, `front`, and `back` — **not** nested inside `merge_variables` or any other object. A misplaced `service_request_number` is silently ignored: the mailpiece is created successfully with no promotion applied and no error returned.
18508
+
18509
+
The SR# must be approved for your account and cover the resource type, size, and mail type of this mailpiece for the promotion to apply. If omitted, no promotion is applied. See our <a href="https://help.lob.com/print-and-mail/building-a-mail-strategy/usps-promotions-through-lob" target="_blank">guide to USPS promotions through Lob</a> for more information.
description: This is in beta. Contact support@lob.com or your account contact to learn more. Not available for `4x6` or `A5` postcard sizes.
@@ -20326,9 +20348,10 @@ components:
20326
20348
campaign_id:
20327
20349
$ref: '#/components/schemas/campaign_id'
20328
20350
failure_reason:
20351
+
type: object
20352
+
nullable: true
20329
20353
allOf:
20330
20354
- $ref: '#/components/schemas/failure_reason'
20331
-
- nullable: true
20332
20355
self_mailer_deletion:
20333
20356
description: Lob uses RESTful HTTP response codes to indicate success or failure of an API request. In general, 2xx indicates success, 4xx indicate an input error, and 5xx indicates an error on Lob's end.
The service request number (SR#) of an approved USPS promotion (for example,
5
+
the Integrated Technology promotion) to apply to this mailpiece. Supported on
6
+
letters, postcards, self mailers, and checks.
7
+
8
+
9
+
This must be a **top-level** field in the create request, alongside `size`,
10
+
`front`, and `back` — **not** nested inside `merge_variables` or any other
11
+
object. A misplaced `service_request_number` is silently ignored: the
12
+
mailpiece is created successfully with no promotion applied and no error
13
+
returned.
14
+
15
+
16
+
The SR# must be approved for your account and cover the resource type, size,
17
+
and mail type of this mailpiece for the promotion to apply. If omitted, no
18
+
promotion is applied. See our
19
+
<a href="https://help.lob.com/print-and-mail/building-a-mail-strategy/usps-promotions-through-lob" target="_blank">guide to USPS promotions through Lob</a>
0 commit comments