Find Customer by Email

Search for a customer using their email address. This endpoint is essential for duplicate prevention - use it before creating new customers to check if they already exist.

Exact Match Only: This endpoint requires an exact email match. It doesn't support partial matching or wildcards.

Case Insensitive: Email matching is case-insensitive. Searching for "USER@EXAMPLE.COM" will find "user@example.com".

Team Scoped: Only searches within the authenticated user's team. The same email can exist in different teams.

Complete Customer Data: Returns the full customer object if found, including all nested objects (addresses, contacts, etc.).

404 vs 200: A 404 response means the customer doesn't exist - this is not an error condition when checking for duplicates. Handle 404s gracefully in your duplicate-prevention workflow.

URL Encoding: Email with special characters must be URL-encoded:

• john+test@example.com becomes john%2Btest%40example.com

• user@my-domain.com becomes user%40my-domain.com Most HTTP clients handle this automatically.

Use Cases:

1. Pre-Creation Check: Check if customer exists before creating to avoid duplicates

2. Customer Lookup: Find customer UUID when you only have their email

3. Import Validation: When importing customers from external systems

4. User Registration: Link users to existing COUNT customers or create new ones

Performance: This endpoint is optimized for email lookups and performs well even with large customer databases. Email is indexed for fast retrieval.

Recommended before creating an invoice or customer to avoid duplicates.