Check a shipment's address with the carrier

PATCH/v2/api/store/{team_slug}/v2/sales_order/{hash_id}/shipment/{id}/validate_address

v2Operation ID v2_public_sales_order_shipment_validate_address

Checks the shipment's shipping address with UPS address validation, for supported countries, and saves the result on the address. An address already checked is not checked again. The answer is the shipment in the older shape, with its status and items. {hash_id} is the order's id; {id} is the shipment's id.

Permission

Any member of the team.

Side effects

• Calls the UPS address validation service once per address and saves the result on the address.

Path parameters

• team_slugstringrequired

  Your team slug, shown as Team ID next to your API key in Profile.

  • Example your-team
• hash_idstringrequired

  The sales order's or quote's id (a hash id). The ord_ unique key and the order number do not work here.

  • Example V4keXwwxMQyXw7
• idstringrequired

  The shipment's id (a hash id).

  • Example qAKg4jO63uFqjs

Request body

This operation takes no request body.

Response

200Successful response.

• dataobjectrequired

  A shipment, in the older shape (app/Transformers/ShipmentTransformer.php, which always includes status and items).

  Child fields (10)

  • idstringrequired
  • status_idstringrequired
  • delivery_notesstring | null
  • delivery_totalinteger | number | string | null

    Older shipping total. Thousandths, an older encoding: 12500 is 12.50. Usually a whole number; an amount finer than a thousandth comes back as a number with a fraction (1234.5 is 1.2345), or as a string ("1234.5") when you send X-Yoprint-Decimal-Format: exact-v1. See Money and quantities.

  • itemsarray of objects

    Shipment lines, in the older shape.

  • order_idstring
  • order_scoped_idstring
  • scoped_idstring
  • shipping_address_idstring | null
  • statusobject | null

    A status, as the status operations return it.

    Child fields (9)

    • colorstringrequired

      A hex color, such as #2196f3.

    • customer_labelstringrequired

      What customers see in the customer portal. When none is set: Pending for start, In Progress for in_progress and pre_production, Completed for end.

    • idstringrequired
    • labelstringrequired

      The status name people see.

    • positionintegerrequired

      Sort order within its list, lowest first.

    • rolestringrequired

      Which list the status belongs to: order, quote, job, shipment, purchase_order, pipeline or customer_message.

    • trashedbooleanrequired

      true for a deleted status.

    • typestringrequired

      start is the first status of its list and end the last; pre_production and in_progress are the ones in between.

      • One of: "start", "pre_production", "in_progress", "end"
    • pipeline_idstring

      The task preset, for pipeline statuses only; absent for other roles.

• statusintegerrequired
• successbooleanrequired

Errors

• 401The API key is missing or wrong (unauthenticated).

• 403You are not allowed to do this. api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only {"message": "Insufficient Permission"}. Other refusals use the error envelope, with unauthorized or user_is_not_authorized.

• 404Not found. page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. code: null, with a message that starts "No query results for": there is no record with that id.

  When

  The shipment is not on this order.

  Fix

  Check the ids.

• 422The request was refused and changed nothing. validation_failed lists what to fix in error.fields; other codes name a business rule, explained in error.message. A few checks answer with only {"message": "..."}. An operation that calls another service (a payment provider, a carrier, an accounting app) can answer connect_timeout ("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.

  When

  The Shopify order was deleted in Shopify (shopify_order_deleted_externally).

  Fix

  Nothing to check: the order is gone in Shopify.

• 500A business rule refused the request (see the operation's errors), or something failed inside YoPrint. Refusals use the error envelope with a code such as action_not_allowed; an unexpected failure answers {"message": "Server Error"}. Repeating a refusal gets the same answer; after an unexpected failure, read the record back before you retry a change.

  When

  The shipment has no shipping address: the body is {"message": "Server Error"}.

  Fix

  Set the shipment's address first.

Related

• GETList the shipments of a sales order/v2/api/store/{team_slug}/v2/sales_order/{unique_key}/shipment

Example request

curl

curl -X PATCH 'https://secure.yoprint.com/v2/api/store/your-team/v2/sales_order/V4keXwwxMQyXw7/shipment/qAKg4jO63uFqjs/validate_address' \  -H 'Authorization: Bearer YOUR_API_KEY' \  -H 'Accept: application/json' \  -H 'X-Yoprint-Decimal-Format: exact-v1'

Example response 200

Response

{
  "data": {
    "delivery_notes": "Leave at reception.",
    "delivery_total": 0,
    "id": "qAKg4jO63uFqjs",
    "items": [],
    "order_id": "V4keXwwxMQyXw7",
    "order_scoped_id": "SO1001",
    "scoped_id": "SHIP-1001",
    "shipping_address_id": "RNG2OuYC20YzXs",
    "status": {
      "color": "#9e9e9e",
      "customer_label": "Pending",
      "id": "43J0pEwV4RKUdO",
      "label": "To pack",
      "position": 1,
      "role": "shipment",
      "trashed": false,
      "type": "start"
    },
    "status_id": "43J0pEwV4RKUdO"
  },
  "status": 200,
  "success": true
}