-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback for “Customers” #620
Comments
Merged
bc-traciporter
added a commit
that referenced
this issue
Oct 31, 2024
<!-- Ticket number or summary of work --> # [Issue-620](#620) ## What changed? Correcting a cut and paste error, changed metafields to customers ## Release notes draft Bug Fix <!-- Provide an entry for the release notes using simple, conversational language. Don't be too technical. Explain how the change will benefit the merchant and link to the feature. Examples: * The newly-released [X feature] is now available to use. Now, you’ll be able to [perform Y action]. * We're happy to announce [X feature], which can help you [perform Y action]. * [X feature] helps you to create [Y response] using the [Z query parameter]. Now, you can deliver [ex, localized shopping experiences for your customers]. * Fixed a bug in the [X endpoint]. Now the [Y field] will appear when you click [Z option]. --> * ## Anything else? <!-- Add related PRs, salient notes, additional ticket numbers, etc. --> ping {names}
Yes but the date string must not be URI nor form encoded. You can encoded |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://developer.bigcommerce.com/docs/rest-management/customers#get-all-customers:
It says "Returns metafields" but it returns customers.
Also worth noting that the date string must not be URI nor form encoded. For example:
Won't work, one must use:
Maybe a bug but if this is an API-wide rule (I just checked with customers) should probably be mentioned here: https://developer.bigcommerce.com/docs/start/about/common-query-params
The text was updated successfully, but these errors were encountered: