Add /v2/users-by-email endpoint #87
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lbalmaceda
force-pushed
the
users-by-email
branch
from
13aab56 to
7625adb
Compare
jeffreylees
reviewed
Nov 8, 2017
README.md
Outdated
| Example: | ||
| ```java | ||
| FieldsFilter filter = new FieldsFilter(...); | ||
| Request<UsersPage> request = mgmt.users().list("johndoe@auth0.com", filter); |
|
I don't know of a document that explains a recommendation between these endpoints. |
aaguiarz
approved these changes
Nov 8, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's not clear if the response is paged or not. The API Explorer says it's not. Also I couldn't find any doc to reference why we encourage the use of this endpoint over the other. @jeffreylees, if you know something please add it or ping me and I'll add it here.
This closes #85