These datetime fields are formatted according to ISO 8601. These two fields respectively specify the time the object in question was created and most recently updated. created_at/updated_at: Most API objects also include values for created_at and updated_at.If your system does not enforce uniqueness on the references you submit, this may result in the wrong one of many objects with the same reference being picked in EasyPost's handling of your API request. The reference values you assign may be used in place of id values in many API endpoints, but we recommend using the EasyPost-assigned id instead because ids are guaranteed to be unique within the system, while reference uniqueness is not enforced. reference: Many API objects also have an optional reference field that may be assigned during creation.For objects where there are many variant types, such as Fees, the object value represents the supertype, and the type represents the subtype for that object. This can be useful for identifying the types of nested objects, or for cases like webhook Events which can contain many different types of result. object: Every first-class EasyPost object includes an object value.
These id values may be used in many API endpoints to refer to an existing object rather than specifying the full object definition for instance in Shipment creation, you may specify the to_address either with all fields ( street1, city, zip, etc.) filled, or you may reuse an existing Address by specifying only the id field value as the matching Address's id, omitting all other fields. Shipments have the prefix "shp_") followed by 32 hex characters. An id consists of a prefix based on the object type (e.g. id: Every EasyPost Object that can be created through the API has an id field that is used to refer to the object in other API calls.There are several attributes that are consistent across all objects: The EasyPost API consists of many object types.