> ## Documentation Index > Fetch the complete documentation index at: https://redo-44af351d-docs-return-item-identifiers-endpoint.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Get customer by email > Retrieve a customer profile by email address. The response includes the customer's name, contact information, location, and any custom fields associated with the profile. Custom fields are returned as `{ fieldName: value }` pairs. ## OpenAPI ````yaml /api-schema/openapi.yaml get /stores/{storeId}/customers openapi: 3.1.0 info: contact: email: engineering-admin@getredo.com name: Redo Engineering description: | ## Endpoints Endpoints are authenticated using the Bearer authorization scheme, using the REDO_API_SECRET. ```txt GET /v2.2/resource HTTP/1.1 Authorization: Bearer 77bb7598b7a972475cc7c7e171ec33af Host: api.getredo.com ``` ## Webhooks Webhooks are authenticated using the Bearer authorization scheme, using a secret supplied by the subscriber. ```txt POST /events HTTP/1.1 Authorization: Bearer subscriberauth123 Host: subscriber.example.com ``` Webhook events are delivered in order for each individual subject (e.g. return). If the response is not a 2xx status code, the event will be retried multiple times before discarding it. title: Redo API version: 2.2.1 servers: - url: https://api.getredo.com/v2.2 security: [] tags: - name: Checkout Buttons - name: Coverage Info - name: Coverage Products - name: Custom Events - name: Customer Portal - name: Customer Subscriptions - name: Customers - name: Inbound Shipments - name: Inventory Items - name: Inventory Levels - name: Invoices - name: Merchant Admin - name: Orders - name: Products - name: Returns - name: Storefront - name: Webhooks paths: /stores/{storeId}/customers: summary: Customers description: Manage customer profiles. get: tags: - Customers summary: Get customer by email description: > Retrieve a customer profile by email address. The response includes the customer's name, contact information, location, and any custom fields associated with the profile. Custom fields are returned as `{ fieldName: value }` pairs. operationId: Customer get parameters: - $ref: '#/components/parameters/store-id.param' - description: Customer email address in: query name: email required: true schema: type: string format: email responses: '200': content: application/json: schema: $ref: '#/components/schemas/customer-read.schema' example: id: 67bd4f1a2e3c8d001a5f9b12 email: jane@example.com firstName: Jane lastName: Smith phoneNumber: '+11234567890' location: street1: 123 Main St street2: Suite 12 city: Seattle state: Washington stateCode: WA postalCode: '98101' country: United States countryCode: US latitude: 47.6062 longitude: -122.3321 customFields: pricing_plan: com.example.yearly status: Active subscription_source: web loyalty_points: 1250 vip_member: true createdAt: '2026-02-20T18:30:00.000Z' updatedAt: '2026-02-24T12:15:00.000Z' description: Customer found '400': content: application/problem+json: schema: $ref: '#/components/schemas/error.schema' description: Missing or invalid email parameter '404': content: application/problem+json: schema: $ref: '#/components/schemas/error.schema' description: No customer found for that email '500': content: application/problem+json: schema: $ref: '#/components/schemas/error.schema' description: Internal server error default: content: application/problem+json: schema: $ref: '#/components/schemas/error.schema' description: Error security: - Bearer: [] components: parameters: store-id.param: description: Store ID in: path name: storeId required: true schema: example: 64e5a8a1af49a89df37e4ee7 type: string schemas: customer-read.schema: description: Customer profile. properties: id: description: Redo customer ID examples: - 67bd4f1a2e3c8d001a5f9b12 type: string email: description: Customer email address format: email examples: - jane@example.com type: string firstName: description: Customer first name examples: - Jane type: string lastName: description: Customer last name examples: - Smith type: string phoneNumber: description: Customer phone number in E.164 format examples: - '+11234567890' type: string location: $ref: '#/components/schemas/customer-location.schema' customFields: description: >- Custom field values as key-value pairs, where keys are field names and values can be strings, numbers, or booleans. DATE custom field values are returned as ISO 8601 datetime strings (e.g., "2026-01-15T12:00:00.000Z"), not Date objects. type: object additionalProperties: oneOf: - type: string - type: number - type: boolean examples: - subscription_source: web status: Active loyalty_points: 1250 vip_member: true signup_date: '2026-02-24T12:15:00.000Z' createdAt: description: >- Timestamp when the customer was created. May be null for older customers created before this field was tracked. format: date-time title: Created at examples: - '2026-02-20T18:30:00.000Z' type: - string - 'null' updatedAt: description: >- Timestamp when the customer was last updated. May be null for older customers created before this field was tracked. format: date-time title: Updated at examples: - '2026-02-24T12:15:00.000Z' type: - string - 'null' required: - id - email title: Customer type: object error.schema: description: >- Problem details. See [RFC 7807 Section 3](https://datatracker.ietf.org/doc/html/rfc7807#section-3). properties: detail: description: Human-readable description of the problem. title: Detail type: string instance: description: A URI reference that identifies this problem. format: uri-reference type: string title: description: Human-readable summary of the problem type. title: Title type: string type: default: about:blank description: A URI reference that identifies the problem type. format: uri-reference type: string title: Problem details type: object customer-location.schema: description: Customer location information. properties: street1: description: Street address line 1 type: string street2: description: Street address line 2 type: string city: description: City name type: string state: description: State or province name examples: - Washington - Ontario type: string stateCode: description: State or province abbreviation examples: - WA - 'ON' type: string postalCode: description: Postal or ZIP code examples: - '12345' - K1A 0B1 type: string country: description: Country name examples: - United States - Canada type: string countryCode: description: ISO 3166-1 alpha-2 country code examples: - US - CA type: string ianaTimeZoneName: description: IANA time zone identifier examples: - America/New_York - America/Los_Angeles type: string latitude: description: Latitude coordinate type: number longitude: description: Longitude coordinate type: number title: Customer Location type: object securitySchemes: Bearer: scheme: bearer type: http ````