> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/v1/integration/php-sdk/localized-products/php-us-us-mail-ocr.md).

# US US Mail

## US US Mail

The PHP SDK supports the Mindee V1 [US Mail API](https://platform.mindee.com/mindee/us_mail).

### Product Specifications

| Specification                  | Details            |
| ------------------------------ | ------------------ |
| Endpoint Name                  | `us_mail`          |
| Recommended Version            | `v3.0`             |
| Supports Polling/Webhooks      | ✔️ Yes             |
| Support Synchronous HTTP Calls | ❌ No               |
| Geography                      | 🇺🇸 United States |

### Quick-Start

Using the [sample below](https://github.com/mindee/client-lib-test-data/blob/main/v1/products/us_mail/default_sample.jpg), we are going to illustrate how to extract the data that we want using the SDK.

<figure><img src="https://github.com/mindee/client-lib-test-data/blob/main/v1/products/us_mail/default_sample.jpg?raw=true" alt="US Mail Sample" width="375"><figcaption></figcaption></figure>

#### Sample Code

```php
<?php

use Mindee\Client;
use Mindee\Product\Us\UsMail\UsMailV3;

// Init a new client
$mindeeClient = new Client("my-api-key");

// Load a file from disk
$inputSource = $mindeeClient->sourceFromPath("/path/to/the/file.ext");

// Parse the file asynchronously
$apiResponse = $mindeeClient->enqueueAndParse(UsMailV3::class, $inputSource);

echo $apiResponse->document;
```

#### Sample Output (rST)

```rst
########
Document
########
:Mindee ID: f9c36f59-977d-4ddc-9f2d-31c294c456ac
:Filename: default_sample.jpg

Inference
#########
:Product: mindee/us_mail v3.0
:Rotation applied: Yes

Prediction
==========
:Sender Name: company zed
:Sender Address:
  :City: Dallas
  :Complete Address: 54321 Elm Street, Dallas, Texas 54321
  :Postal Code: 54321
  :State: TX
  :Street: 54321 Elm Street
:Recipient Names: Jane Doe
:Recipient Addresses:
  +-----------------+-------------------------------------+-------------------+-------------+------------------------+-------+---------------------------+-----------------+
  | City            | Complete Address                    | Is Address Change | Postal Code | Private Mailbox Number | State | Street                    | Unit            |
  +=================+=====================================+===================+=============+========================+=======+===========================+=================+
  | Detroit         | 1234 Market Street PMB 4321, Det... | False             | 12345       | 4321                   | MI    | 1234 Market Street        |                 |
  +-----------------+-------------------------------------+-------------------+-------------+------------------------+-------+---------------------------+-----------------+
:Return to Sender: False
```

## Field Types

### Standard Fields

These fields are generic and used in several products.

#### BaseField

Each prediction object contains a set of fields that inherit from the generic `BaseField` class. A typical `BaseField` object will have the following attributes:

* **value** (`float|string`): corresponds to the field value. Can be `null` if no value was extracted.
* **confidence** (`float`): the confidence score of the field prediction.
* **boundingBox** (`[Point, Point, Point, Point]`): contains exactly 4 relative vertices (points) coordinates of a right rectangle containing the field in the document.
* **polygon** (`Point[]`): contains the relative vertices coordinates (`Point`) of a polygon containing the field in the image.
* **pageId** (`integer`): the ID of the page, always `null` when at document-level.
* **reconstructed** (`bool`): indicates whether an object was reconstructed (not extracted as the API gave it).

{% hint style="info" %}
A `Point` simply refers to a list of two numbers (`[float, float]`).
{% endhint %}

Aside from the previous attributes, all basic fields have access to a custom `__toString` method that can be used to print their value as a string.

#### StringField

The text field `StringField` implements the following:

* **value** (`string`): represents the value of the field as a string.
* **rawValue** (`string`): the value of the string as it appears on the document.

#### BooleanField

The boolean field `BooleanField` only has one constraint: its **value** is an optional `?bool`.

### Specific Fields

Fields which are specific to this product; they are not used in any other product.

#### Recipient Addresses Field

The addresses of the recipients.

A `UsMailV3RecipientAddress` implements the following attributes:

* **city** (`string`): The city of the recipient's address.
* **complete** (`string`): The complete address of the recipient.
* **isAddressChange** (`bool`): Indicates if the recipient's address is a change of address.
* **postalCode** (`string`): The postal code of the recipient's address.
* **privateMailboxNumber** (`string`): The private mailbox number of the recipient's address.
* **state** (`string`): Second part of the ISO 3166-2 code, consisting of two letters indicating the US State.
* **street** (`string`): The street of the recipient's address.
* **unit** (`string`): The unit number of the recipient's address. Fields which are specific to this product; they are not used in any other product.

#### Sender Address Field

The address of the sender.

A `UsMailV3SenderAddress` implements the following attributes:

* **city** (`string`): The city of the sender's address.
* **complete** (`string`): The complete address of the sender.
* **postalCode** (`string`): The postal code of the sender's address.
* **state** (`string`): Second part of the ISO 3166-2 code, consisting of two letters indicating the US State.
* **street** (`string`): The street of the sender's address.

### Attributes

The following fields are extracted for US Mail V3:

#### Return to Sender

**isReturnToSender** : Whether the mailing is marked as return to sender.

```php
echo $result->document->inference->prediction->isReturnToSender->value;
```

#### Recipient Addresses

**recipientAddresses** (\[[UsMailV3RecipientAddress](#recipient-addresses-field)]): The addresses of the recipients.

```php
foreach ($result->document->inference->prediction->recipientAddresses as $recipientAddressesElem)
{
    echo $recipientAddressesElem->value;
}
```

#### Recipient Names

**recipientNames** : The names of the recipients.

```php
foreach ($result->document->inference->prediction->recipientNames as $recipientNamesElem)
{
    echo $recipientNamesElem->value;
}
```

#### Sender Address

**senderAddress** ([UsMailV3SenderAddress](#sender-address-field)): The address of the sender.

```php
echo $result->document->inference->prediction->senderAddress->value;
```

#### Sender Name

**senderName** : The name of the sender.

```php
echo $result->document->inference->prediction->senderName->value;
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mindee.com/v1/integration/php-sdk/localized-products/php-us-us-mail-ocr.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
