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. 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. 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. 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. These two fields respectively specify the time the object in question was created and most recently updated. These datetime fields are formatted according to ISO 8601.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |