Addresses
The Addresses API allows you to organize customer addresses. Addresses are a sub-resource of a Customer. A Customer may have multiple addresses, such as home
, work
and neighbor
. You are able to use a customer with an implicit Bearer token. This is recommend for client-side interactions. Or you can use a client_credentials Bearer token. This is recommended for back end interactions.
The Address object
Attribute | Type | Description |
|
| The unique identifier for this address |
|
| The type represents the object being returned |
|
| The first name of the recipient on this address |
|
| The last name of the recipient on this address |
|
| The name for the address saved. Such as |
|
| A phone number for this address |
|
| Any delivery instructions associated with this addresses |
|
| The company name at this address |
|
| Usually the street name |
|
| Usually the unit or apartment number |
|
| The city for this address |
|
| The county for this address |
|
| The ZIP, postcode or other postal reference for this address |
|
| A two digit code for this country address. This is a |
Last updated