Jump to main content

# Logos

The DocumentServicesAPI, DocServicesAPI, and ExpereAPI's support logo functionality as a standard offering for lenders who wish to insert a unique ancillary logo in a transaction.

Logos are implemented as a post-processing event submitted on a request in the AncillaryOutputOptions object and defined through a single object, Logo, containing four child elements:

- HeightInInches: specifies the height of the logo.
- WidthInInches: specifies the width of the logo.
- Justification: specifies the header location of the logo with available values of "top," "center," or "right."
- Placement: applies the logo to a desired page or set of pages with available values of "AllPages," "FirstPageOnly," or "AllExceptFirstPage."
- AlternativeText: applies a string value used for hover text in ADA-compliant documents.

Note: Users must pass in either a `<HeightInInches/>` or `<WidthInInches/>` element. If only passing in one of the parameters, Expere will auto-scale the logo.

When using custom logos: custom logos where the logo image is passed in the transaction, using one of the xpaths below, will continue to be honored. The Ancillary Logo will be ignored for documents using the transaction logo.

- /Txn/LogoDesc
- /Txn/LogoLeftDesc
- /Txn/LogoCenterDesc
- /Txn/LogoRightDesc

Custom logos where the logo image is within the custom content (embedded in the REQ) will print both the Ancillary logo and the logo embedded in the REQ. Users can adjust for this by using the Generate API and specify which documents the Ancillary logo should be applied to, or, remove the custom logo from custom content.

## Situations where logos are not applied

There are certain situations where logos will not be applied.

- Static documents: a logo could inadvertently appear over static text.
- Recordable documents: applying a logo could modify margins which are compliant in nature.
- Dynamic documents that use the Integrated Disclosure StyleGuide: applying a logo is prohibited as TRID documents and regulations are used to match model forms
- Custom logos: see When using custom logos above

## Recommended Practices

Consider the following when working with logos:

- Provide both height and width values to avoid any image distortion.
- It is important to use a higher-resolution graphic file, at least 300 pixels per inch. A lower resolution image is harder to scale up.
- When working with non-recordable documents, logos are limited in height to 1.5 inches.
- Logo files are configured to allow a maximum size of 600 kb to accommodate base64 formatting.

## Supported File Formats

Supported file formats consist of the following:

- .gif
- .png
- .jpg/.jpeg
- .bmp