Skip to content

Get/Upsert customer endpoints - #89

Open
Josh Moody (joshmoody24) wants to merge 1 commit into
release/2.2from
josh/upsert-customer
Open

Get/Upsert customer endpoints#89
Josh Moody (joshmoody24) wants to merge 1 commit into
release/2.2from
josh/upsert-customer

Conversation

@joshmoody24

Copy link
Copy Markdown
Contributor
image image

@joshmoody24 Josh Moody (joshmoody24) changed the title Upsert customer endpoint Get/Upsert customer endpoints Feb 5, 2026
Comment on lines +17 to +20
phoneNumber:
description: Customer phone number in E.164 format (e.g., +12345678900)
minLength: 1
type: string

@joshmoody24 Josh Moody (joshmoody24) Feb 5, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My biggest question is, should we include phoneNumber in the list of possible input identifiers, or just have email for now?

Allowing phoneNumber opens up the API to the can of worms that is customer merging. And since it's potentially shared, if someone just gives us a phoneNumber (no email) it would just find the first of potentially many customers to update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants