Retrieve Detailed Customer Information

The Retrieve Customer endpoint returns the complete profile record for a specific customer, identified by their unique ID. The response includes core contact fields such as name, email address, phone number, and country, along with any additional attributes recorded against the customer profile. This data is essential for verifying customer identity during transaction processing, customer support operations, and compliance workflows.

Use the include query parameter to load related data such as associated addresses, and tags in a single request. This endpoint integrates directly with the Create Payment Link and Update Customer workflows, ensuring that downstream operations always operate on accurate and current customer records.

GET/client/customers/{customer_id}
Sandbox: https://api.payiano.dev/v1/client/customers/{customer_id}
Live: https://api.payiano.com/v1/client/customers/{customer_id}
Security
  • Authorization header with access token is required to access this endpoint: Bearer ACCESS-TOKEN
  • Your access token should be associated to this permission client.customers.view
Request
Request body schema:
application/json
Path parameters:
customer_id
required
Type: ulid
Length: 26

The unique ID assigned to each customer which is generated by our system using the ULID format. Each ID is precisely 26 characters long, ensuring a unique and consistent identifier for every customer. This ULID is automatically created by our system and is used to uniquely identify and track each customer in our database.

Query parameters:
identify_by
Type: enum|null
Possible values:
JSON
[
"id", "reference_id" ]

This attribute specifies which identifier is being used to interact with a resource in the Payiano API. It helps the system understand how to identify resource when processing API requests. By default, the identify_by attribute is set to id, so you only need to specify it if you're using a different identifier.

includes
Type: array_of_enums|null
Possible values:
JSON
[
"customer.billing_address", "customer.billing_address.country", "customer.metadata", "customer.shipping_address", "customer.shipping_address.country", "customer.tags", "customer.tags.metadata" ]

A list of additional customer related objects to eager-load and return with the response. Pass only the relations you need to keep response payloads lean. See Including Resources for the full list of supported include values and usage details.

Response
200
Response schema:
application/json
Response body:
customer
Type: object

The full customer record including name, contact details, and associated metadata.

id
Type: ulid
Length: 26

The unique ID assigned to each customer which is generated by our system using the ULID format. Each ID is precisely 26 characters long, ensuring a unique and consistent identifier for every customer. This ULID is automatically created by our system and is used to uniquely identify and track each customer in our database.

name
Type: string
Min: 2
Max: 255

This is the fundamental attribute representing the customer's full legal or preferred name. It's used in all forms of communication and identification. It's crucial for personalization and ensures that all correspondences and documents are correctly addressed.

email
Type: string|null
Min: 5
Max: 255

The email address is a key point of contact for digital communication. It's used for sending transactional emails, marketing material and support communications.

billing_emails
Type: array_of_strings
Max: 20

In addition to the primary email, customers might have separate email addresses specifically for billing purposes. This field can store multiple emails, ensuring that all billing-related documents reach the appropriate contacts, which is especially useful in business settings.

cc_emails
Type: array_of_strings
Max: 20

These are carbon copy email addresses where copies of communications are sent. This is particularly useful in a business context where multiple parties, like account managers or financial departments, need to be kept in the loop.

shipping_address_as_billing_address
Type: boolean
Default: true

Another boolean attribute indicating whether the customer's shipping address is identical to their billing address. This simplifies the process for customers who use the same address for both purposes and streamlines data entry and management.

billing_email_as_customer_email
Type: boolean
Default: true

This attribute indicates whether the customer's primary email address, which is used for general communication and account management, is the same as the email address used specifically for billing purposes.

phone_number
Type: string|null

This attribute stores the customer's telephone or mobile number. It's essential for direct contact, SMS notifications, and can also be used in cases where email communication is insufficient or inappropriate.

type
Type: enum|null
Possible values:
JSON
[
"individual", "business" ]

This attribute is used to differentiate between types of customers, such as individual consumers, business clients, or other classifications. The type can influence how the profile is managed and what kind of communication is sent.

gender
Type: enum|null
Possible values:
JSON
[
"male", "female" ]

Recording the customer's gender can help in creating more personalized marketing strategies and customer interactions. It's useful for demographic segmentation and can be leveraged to tailor products, services, and communication to better align with the customer's preferences.

country_code
Type: string|null

Specify the unique two-letter country code ( e.g EG, SA or AE ) corresponding to the country where your customer is based. This code is part of the standard international country codes set by the ISO .

reference_id
Type: string|null
Max: 50

It's a unique identifier assigned to each customer. It's primary role is to distinguish one customer from another, ensuring that each customer can be individually tracked and managed without any confusion. Please note that duplicate values are not allowed. Only alpha-numeric characters, dashes, and underscores are allowed: [A-Za-z0-9-_]. The reference_id value is used to Identify Resource when you consume any customer endpoint with sending identify_by query parameter with value reference_id.

is_active
Type: boolean
Default: true

Indicates whether the customer is currently active. Set to true to enable the customer and make it available in listings and operations; set to false to deactivate it without removing it from the system.

description
Type: string|null
Max: 10000

This free-form text field allows for adding additional notes or details about the customer. It can include information like customer preferences, special instructions, past interactions, or any other relevant data that doesn't fit into more structured fields.

tags
Type: array_of_objects
Max: 20

The list of customer tags objects.

id
Type: ulid
Length: 26

The unique ID assigned to each customer tag which is generated by our system using the ULID format. Each ID is precisely 26 characters long, ensuring a unique and consistent identifier for every customer tag. This ULID is automatically created by our system and is used to uniquely identify and track each customer tag in our database.

name
Type: string
Min: 1
Max: 100

This attribute serves as the identifier or label for the group. It's a concise and clear title that represents the essence of the group. For instance, a name could be 'Frequent Buyers' or 'Newsletter Subscribers'. This attribute should be chosen to reflect the common characteristic or purpose that links the customers in this tag, making it easy to identify and reference the group at a glance. Please note that duplicate values are not allowed. Only alpha-numeric characters, dashes, underscores, and spaces are allowed: [A-Za-z0-9-_ ].

is_active
Type: boolean
Default: true

Indicates whether the customer tag is currently active. Set to true to enable the customer tag and make it available in listings and operations; set to false to deactivate it without removing it from the system.

reference_id
Type: string|null
Max: 50

It's a unique identifier assigned to each customer tag. It's primary role is to distinguish one customer tag from another, ensuring that each customer tag can be individually tracked and managed without any confusion. Please note that duplicate values are not allowed. Only alpha-numeric characters, dashes, and underscores are allowed: [A-Za-z0-9-_]. The reference_id value is used to Identify Resource when you consume any customer tag endpoint with sending identify_by query parameter with value reference_id.

description
Type: string|null
Max: 10000

This attribute provides more detailed information about the customer tag. It's where you can explain the purpose or characteristics of the group in more depth. For example, for a tag named 'Frequent Buyers', the description might elaborate on criteria like “Customers who make purchases more than twice a month.” This attribute is particularly useful for understanding the context and nuances of the customer group, guiding how you interact with and cater to this segment.

metadata
Type: object|null

The customer tag metadata model details. Metadata serves as a tool for keeping extra, organized details about a resource. For example, you can use it to store a user's preferences like preferred color, notes or any other data that aids in personalizing services, improving customer relations, or optimizing internal workflows. This information isn't utilized by Payiano – meaning it's not involved in authorizing or declining transactions and remains invisible to your users. Its value is entirely private for your internal use, and we ensure it remains confidential, not shared with any external parties.

info
Type: array_of_objects
Max: 50

This array consists of objects, each containing a key and a value. These pairs of key-value are structured in a way that's more suitable for programmatic access. You can add up to 50 objects.

key
Type: string
Min: 1
Max: 50

It's a unique identifier to avoid confusion or data overlap. The keys serve as identifiers for the corresponding values, making it easier to retrieve specific pieces of information as needed.

value
Type: string
Min: 1
Max: 255

The value is the actual data associated with that key. It could be a simple string, a number, a URL, or any other data format that conveys the necessary information.

list
Type: array_of_strings
Max: 50

The list attribute is particularly useful for scenarios where the data needs to be presented in a straightforward, unstructured format. It's ideal for quick overviews, simple data logging, or when the information does not require the more complex organization that nested JSON objects provide. Please notice that duplicate values are not allowed, you can add up to 50 item and the max list item length is 255 characters.

is_deleted
Type: boolean
Default: false

Indicates whether the customer tag has been soft-deleted. A true value means the record is marked as deleted and excluded from standard listings; a false value means it is active. Soft-deleted records remain in the database and can be restored.

created_at
Type: datetime

The created datetime of the customer tag. This attribute can be formatted as an ISO 8601 string or a UNIX timestamp in milliseconds, depending on the preferred datetime format specified in the request header (e.g., 2024-08-04T14:22:01Z or 1722572118554). By default, the format is UNIX timestamp in milliseconds.

updated_at
Type: datetime

The updated datetime of the customer tag. This attribute can be formatted as an ISO 8601 string or a UNIX timestamp in milliseconds, depending on the preferred datetime format specified in the request header (e.g., 2024-08-04T14:22:01Z or 1722572118554). By default, the format is UNIX timestamp in milliseconds.

deleted_at
Type: datetime|null

The deleted datetime of the customer tag. This attribute can be formatted as an ISO 8601 string or a UNIX timestamp in milliseconds, depending on the preferred datetime format specified in the request header (e.g., 2024-08-04T14:22:01Z or 1722572118554). By default, the format is UNIX timestamp in milliseconds.

metadata
Type: object|null

The customer metadata model details. Metadata serves as a tool for keeping extra, organized details about a resource. For example, you can use it to store a user's preferences like preferred color, notes or any other data that aids in personalizing services, improving customer relations, or optimizing internal workflows. This information isn't utilized by Payiano – meaning it's not involved in authorizing or declining transactions and remains invisible to your users. Its value is entirely private for your internal use, and we ensure it remains confidential, not shared with any external parties.

info
Type: array_of_objects
Max: 50

This array consists of objects, each containing a key and a value. These pairs of key-value are structured in a way that's more suitable for programmatic access. You can add up to 50 objects.

key
Type: string
Min: 1
Max: 50

It's a unique identifier to avoid confusion or data overlap. The keys serve as identifiers for the corresponding values, making it easier to retrieve specific pieces of information as needed.

value
Type: string
Min: 1
Max: 255

The value is the actual data associated with that key. It could be a simple string, a number, a URL, or any other data format that conveys the necessary information.

list
Type: array_of_strings
Max: 50

The list attribute is particularly useful for scenarios where the data needs to be presented in a straightforward, unstructured format. It's ideal for quick overviews, simple data logging, or when the information does not require the more complex organization that nested JSON objects provide. Please notice that duplicate values are not allowed, you can add up to 50 item and the max list item length is 255 characters.

billing_address
Type: object|null

The customer default billing address model details.

id
Type: ulid
Length: 26

The unique ID assigned to each customer address which is generated by our system using the ULID format. Each ID is precisely 26 characters long, ensuring a unique and consistent identifier for every customer address. This ULID is automatically created by our system and is used to uniquely identify and track each customer address in our database.

country_code
Type: string

Specify the unique two-letter country code ( e.g EG, SA or AE ) corresponding to the country where customer is located. This code is part of the standard international country codes set by the ISO .

type
Type: enum
Possible values:
JSON
[
"billing_address", "shipping_address" ]

This attribute is used to differentiates between types of customer addresses, such as billing or shipping address.

is_default
Type: boolean
Default: false

This attribute specifies if the address is the default one selected for the customer for billing or shipping purposes. It comes into play when the user is directed to the checkout page or when an order is being delivered to them.

reference_id
Type: string|null
Max: 50

It's a unique identifier assigned to each customer address. It's primary role is to distinguish one customer address from another, ensuring that each customer address can be individually tracked and managed without any confusion. Please note that duplicate values are not allowed. Only alpha-numeric characters, dashes, and underscores are allowed: [A-Za-z0-9-_]. The reference_id value is used to Identify Resource when you consume any customer address endpoint with sending identify_by query parameter with value reference_id.

line_one
Type: string|null
Min: 2
Max: 255

The primary address line, typically containing the building or house number and street name. This field is required and must precisely identify the street-level location for deliveries, correspondence, and geographic lookups.

line_two
Type: string|null
Min: 2
Max: 255

An optional secondary address line used for additional information like apartment, suite, or building numbers that help refine the location for delivery services.

city
Type: string|null
Min: 2
Max: 50

This attribute specifies the city in which the address is located. It's essential for routing mail and deliveries within the correct geographical area.

state
Type: string|null
Min: 2
Max: 50

The state or region attribute further narrows down the location, especially in countries with large geographical areas divided into states, provinces, or regions.

zip_code
Type: string|null
Min: 2
Max: 30

Also known as postal code in some regions, this numeric or alphanumeric code is critical for sorting mail and determining delivery routes with precision.

phone_number
Type: string|null
Max: 30

A primary contact number that can be a mobile or cellular number, providing a direct line to the individual or entity associated with the address.

landline_number
Type: string|null
Max: 30

An alternative to the mobile number, this is a fixed-line telephone number associated with the location, useful for contact purposes where mobile signals may be unreliable.

fax_number
Type: string|null
Max: 30

An optional fax number associated with the address. Used to receive documents transmitted over telephone lines in business or institutional contexts where fax communication is still supported.

first_name
Type: string|null
Min: 2
Max: 50

The given name of the individual associated with the address, important for personalizing communication and ensuring the correct recipient for mail or services.

last_name
Type: string|null
Min: 2
Max: 50

The family or surname of the individual, completing the personal identification and used in conjunction with the first name for full clarity on the recipient's identity.

location
Type: object|null

This attribute is used to offer a precise, geographical identification of a place, which is crucial for various applications like mapping, navigation, and location-based services.

lat
Type: decimal
Min: -90
Max: 90

The geographic latitude of the address, expressed in decimal degrees. Valid values range from -90 (south pole) to 90 (north pole). Used together with longitude to pinpoint the exact location on a map or coordinate system.

lng
Type: decimal
Min: -180
Max: 180

The geographic longitude of the address, expressed in decimal degrees. Valid values range from -180 (west) to 180 (east). Combined with latitude, provides the precise GPS coordinates required for mapping and location-based services.

note
Type: string|null
Min: 2
Max: 255

This free-text field allows for additional information or special instructions related to the address or delivery preferences to be included.

customer_id
Type: ulid

This field is the key to associating each address with the correct customer account, enhancing the personalization and accuracy of the transaction process. It not only enhances transaction precision but also contributes significantly to effective customer relationship management and data analysis.

country
Type: object

A country object containing the official name, two-letter ISO code, flag emoji, primary language, international dialing code, and ISO currency code.

name
Type: string

The official name of the country in English or In Arabic if the Accepted-Language header is set to ar. This is the commonly recognized name that would be used in international contexts and is essential for any application that references countries by name.

flag
Type: string

A Unicode representation of the country's flag. Unlike an image URL, Unicode flags are character codes that render as the country's flag emoji across compatible digital platforms. This allows for easy integration of flags into text-based content and interfaces without needing external images.

lang
Type: string|null

This attribute represents the primary language spoken in the country. It's typically expressed in ISO 639-1 format, a two-letter code identifying the language, making it easier for applications to adapt content or interfaces according to the user's region.

code
Type: string

The unique two-letter country code ( e.g EG, SA or AE ) corresponding to the country. This code is part of the standard international country codes set by the ISO .

dial_code
Type: string

The international dialing code for the country, such as +1 for the United States, +44 for the United Kingdom or +20 for Egypt. This code is crucial for making international telephone calls and can be used in applications that require user phone number verification.

currency_code
Type: string

This attribute describes the official currency used in the country, typically denoted by its ISO currency code, such as USD for the United States Dollar, EUR for the Euro or EGP for Egyptian Pound.

is_deleted
Type: boolean
Default: false

Indicates whether the customer address has been soft-deleted. A true value means the record is marked as deleted and excluded from standard listings; a false value means it is active. Soft-deleted records remain in the database and can be restored.

created_at
Type: datetime

The created datetime of the customer address. This attribute can be formatted as an ISO 8601 string or a UNIX timestamp in milliseconds, depending on the preferred datetime format specified in the request header (e.g., 2024-08-04T14:22:01Z or 1722572118554). By default, the format is UNIX timestamp in milliseconds.

updated_at
Type: datetime

The updated datetime of the customer address. This attribute can be formatted as an ISO 8601 string or a UNIX timestamp in milliseconds, depending on the preferred datetime format specified in the request header (e.g., 2024-08-04T14:22:01Z or 1722572118554). By default, the format is UNIX timestamp in milliseconds.

deleted_at
Type: datetime|null

The deleted datetime of the customer address. This attribute can be formatted as an ISO 8601 string or a UNIX timestamp in milliseconds, depending on the preferred datetime format specified in the request header (e.g., 2024-08-04T14:22:01Z or 1722572118554). By default, the format is UNIX timestamp in milliseconds.

shipping_address
Type: object|null

The customer default shipping address model details.

id
Type: ulid
Length: 26

The unique ID assigned to each customer address which is generated by our system using the ULID format. Each ID is precisely 26 characters long, ensuring a unique and consistent identifier for every customer address. This ULID is automatically created by our system and is used to uniquely identify and track each customer address in our database.

country_code
Type: string

Specify the unique two-letter country code ( e.g EG, SA or AE ) corresponding to the country where customer is located. This code is part of the standard international country codes set by the ISO .

type
Type: enum
Possible values:
JSON
[
"billing_address", "shipping_address" ]

This attribute is used to differentiates between types of customer addresses, such as billing or shipping address.

is_default
Type: boolean
Default: false

This attribute specifies if the address is the default one selected for the customer for billing or shipping purposes. It comes into play when the user is directed to the checkout page or when an order is being delivered to them.

reference_id
Type: string|null
Max: 50

It's a unique identifier assigned to each customer address. It's primary role is to distinguish one customer address from another, ensuring that each customer address can be individually tracked and managed without any confusion. Please note that duplicate values are not allowed. Only alpha-numeric characters, dashes, and underscores are allowed: [A-Za-z0-9-_]. The reference_id value is used to Identify Resource when you consume any customer address endpoint with sending identify_by query parameter with value reference_id.

line_one
Type: string|null
Min: 2
Max: 255

The primary address line, typically containing the building or house number and street name. This field is required and must precisely identify the street-level location for deliveries, correspondence, and geographic lookups.

line_two
Type: string|null
Min: 2
Max: 255

An optional secondary address line used for additional information like apartment, suite, or building numbers that help refine the location for delivery services.

city
Type: string|null
Min: 2
Max: 50

This attribute specifies the city in which the address is located. It's essential for routing mail and deliveries within the correct geographical area.

state
Type: string|null
Min: 2
Max: 50

The state or region attribute further narrows down the location, especially in countries with large geographical areas divided into states, provinces, or regions.

zip_code
Type: string|null
Min: 2
Max: 30

Also known as postal code in some regions, this numeric or alphanumeric code is critical for sorting mail and determining delivery routes with precision.

phone_number
Type: string|null
Max: 30

A primary contact number that can be a mobile or cellular number, providing a direct line to the individual or entity associated with the address.

landline_number
Type: string|null
Max: 30

An alternative to the mobile number, this is a fixed-line telephone number associated with the location, useful for contact purposes where mobile signals may be unreliable.

fax_number
Type: string|null
Max: 30

An optional fax number associated with the address. Used to receive documents transmitted over telephone lines in business or institutional contexts where fax communication is still supported.

first_name
Type: string|null
Min: 2
Max: 50

The given name of the individual associated with the address, important for personalizing communication and ensuring the correct recipient for mail or services.

last_name
Type: string|null
Min: 2
Max: 50

The family or surname of the individual, completing the personal identification and used in conjunction with the first name for full clarity on the recipient's identity.

location
Type: object|null

This attribute is used to offer a precise, geographical identification of a place, which is crucial for various applications like mapping, navigation, and location-based services.

lat
Type: decimal
Min: -90
Max: 90

The geographic latitude of the address, expressed in decimal degrees. Valid values range from -90 (south pole) to 90 (north pole). Used together with longitude to pinpoint the exact location on a map or coordinate system.

lng
Type: decimal
Min: -180
Max: 180

The geographic longitude of the address, expressed in decimal degrees. Valid values range from -180 (west) to 180 (east). Combined with latitude, provides the precise GPS coordinates required for mapping and location-based services.

note
Type: string|null
Min: 2
Max: 255

This free-text field allows for additional information or special instructions related to the address or delivery preferences to be included.

customer_id
Type: ulid

This field is the key to associating each address with the correct customer account, enhancing the personalization and accuracy of the transaction process. It not only enhances transaction precision but also contributes significantly to effective customer relationship management and data analysis.

country
Type: object

A country object containing the official name, two-letter ISO code, flag emoji, primary language, international dialing code, and ISO currency code.

name
Type: string

The official name of the country in English or In Arabic if the Accepted-Language header is set to ar. This is the commonly recognized name that would be used in international contexts and is essential for any application that references countries by name.

flag
Type: string

A Unicode representation of the country's flag. Unlike an image URL, Unicode flags are character codes that render as the country's flag emoji across compatible digital platforms. This allows for easy integration of flags into text-based content and interfaces without needing external images.

lang
Type: string|null

This attribute represents the primary language spoken in the country. It's typically expressed in ISO 639-1 format, a two-letter code identifying the language, making it easier for applications to adapt content or interfaces according to the user's region.

code
Type: string

The unique two-letter country code ( e.g EG, SA or AE ) corresponding to the country. This code is part of the standard international country codes set by the ISO .

dial_code
Type: string

The international dialing code for the country, such as +1 for the United States, +44 for the United Kingdom or +20 for Egypt. This code is crucial for making international telephone calls and can be used in applications that require user phone number verification.

currency_code
Type: string

This attribute describes the official currency used in the country, typically denoted by its ISO currency code, such as USD for the United States Dollar, EUR for the Euro or EGP for Egyptian Pound.

is_deleted
Type: boolean
Default: false

Indicates whether the customer address has been soft-deleted. A true value means the record is marked as deleted and excluded from standard listings; a false value means it is active. Soft-deleted records remain in the database and can be restored.

created_at
Type: datetime

The created datetime of the customer address. This attribute can be formatted as an ISO 8601 string or a UNIX timestamp in milliseconds, depending on the preferred datetime format specified in the request header (e.g., 2024-08-04T14:22:01Z or 1722572118554). By default, the format is UNIX timestamp in milliseconds.

updated_at
Type: datetime

The updated datetime of the customer address. This attribute can be formatted as an ISO 8601 string or a UNIX timestamp in milliseconds, depending on the preferred datetime format specified in the request header (e.g., 2024-08-04T14:22:01Z or 1722572118554). By default, the format is UNIX timestamp in milliseconds.

deleted_at
Type: datetime|null

The deleted datetime of the customer address. This attribute can be formatted as an ISO 8601 string or a UNIX timestamp in milliseconds, depending on the preferred datetime format specified in the request header (e.g., 2024-08-04T14:22:01Z or 1722572118554). By default, the format is UNIX timestamp in milliseconds.

created_at
Type: datetime

The created datetime of the customer. This attribute can be formatted as an ISO 8601 string or a UNIX timestamp in milliseconds, depending on the preferred datetime format specified in the request header (e.g., 2024-08-04T14:22:01Z or 1722572118554). By default, the format is UNIX timestamp in milliseconds.

updated_at
Type: datetime

The updated datetime of the customer. This attribute can be formatted as an ISO 8601 string or a UNIX timestamp in milliseconds, depending on the preferred datetime format specified in the request header (e.g., 2024-08-04T14:22:01Z or 1722572118554). By default, the format is UNIX timestamp in milliseconds.

Response sample:
JSON
1
{
2
"customer": {
3 "id": "01hqjp3f48879znt9v4dysrk2r", 4 "name": "Mohsen Ali", 5 "email": "mohsen@gawaab.com", 6
"billing_emails": [
7 "shady.abbas@gawaab.com", 8 "diab.maged@gawaab.com" 9 ], 10
"cc_emails": [
11 "ramy.tarek@gawaab.com", 12 "dina.mourad@gawaab.com" 13 ], 14 "shipping_address_as_billing_address": true, 15 "billing_email_as_customer_email": true, 16 "phone_number": "+201000333000", 17 "type": "individual", 18 "gender": "male", 19 "country_code": "EG", 20 "reference_id": "7193edd2-7574-3b76-9103-e0e37580129b", 21 "is_active": true, 22 "description": "Business development head at Gawaab", 23
"tags": [
24
{
25 "id": "01hqjp31wcww3jhnagehc16r04", 26 "name": "Frequent Buyers", 27 "is_active": true, 28 "reference_id": "7193edd2-7574-3b76-9103-e0e37580129b", 29 "description": "Customers who make purchases more than twice a month.", 30
"metadata": {
31
"info": [
32
{
33 "key": "Company name", 34 "value": "Pyngy" 35 } 36 ], 37
"list": [
38 "Cairo, Nasr City, 7th District, Building 12 floor 5" 39 ] 40 }, 41 "is_deleted": false, 42 "created_at": "1722572118554", 43 "updated_at": "1722572118554", 44 "deleted_at": null 45 } 46 ], 47
"metadata": {
48
"info": [
49
{
50 "key": "Company name", 51 "value": "Pyngy" 52 } 53 ], 54
"list": [
55 "Cairo, Nasr City, 7th District, Building 12 floor 5" 56 ] 57 }, 58
"billing_address": {
59 "id": "01ht3tph1szfa5b02qsay22hk1", 60 "country_code": "EG", 61 "type": "billing_address", 62 "is_default": true, 63 "reference_id": "96bf2bca-61c0-3eba-bc85-bfae3bcfd85f", 64 "line_one": "7th Makram Ebid, Nasr City", 65 "line_two": "Building 174, apartment 12", 66 "city": "Cairo", 67 "state": "Nasr City", 68 "zip_code": "11321", 69 "phone_number": "+201000333000", 70 "landline_number": "6546543213216", 71 "fax_number": "5456464646", 72 "first_name": "Mohsen", 73 "last_name": "Osama", 74
"location": {
75 "lat": 21.32, 76 "lng": 12.63 77 }, 78 "note": null, 79 "customer_id": "01hqjp3f48879znt9v4dysrk2r", 80
"country": {
81 "name": "Egypt", 82 "flag": "🇪🇬", 83 "lang": "AR", 84 "code": "EG", 85 "dial_code": "+20", 86 "currency_code": "EGP" 87 }, 88 "is_deleted": false, 89 "created_at": "1722572118554", 90 "updated_at": "1722572118554", 91 "deleted_at": null 92 }, 93
"shipping_address": {
94 "id": "01ht3tph1szfa5b02qsay22hk1", 95 "country_code": "EG", 96 "type": "shipping_address", 97 "is_default": true, 98 "reference_id": "96bf2bca-61c0-3eba-bc85-bfae3bcfd85f", 99 "line_one": "7th Makram Ebid, Nasr City", 100 "line_two": "Building 174, apartment 12", 101 "city": "Cairo", 102 "state": "Nasr City", 103 "zip_code": "11321", 104 "phone_number": "+201000333000", 105 "landline_number": "6546543213216", 106 "fax_number": "5456464646", 107 "first_name": "Mohsen", 108 "last_name": "Osama", 109
"location": {
110 "lat": 21.32, 111 "lng": 12.63 112 }, 113 "note": null, 114 "customer_id": "01hqjp3f48879znt9v4dysrk2r", 115
"country": {
116 "name": "Egypt", 117 "flag": "🇪🇬", 118 "lang": "AR", 119 "code": "EG", 120 "dial_code": "+20", 121 "currency_code": "EGP" 122 }, 123 "is_deleted": false, 124 "created_at": "1722572118554", 125 "updated_at": "1722572118554", 126 "deleted_at": null 127 }, 128 "created_at": "1722572118554", 129 "updated_at": "1722572118554" 130 } 131}