Reseller Edit User by Email API
Allow resellers to update user account details using email address lookup
Reseller Edit User by Email API
Update user account details using their email address. Convenient when you don't have the user's ID readily available.
Email Lookup
Find and update by email.
Same Capabilities
Full edit functionality.
Convenient
No ID lookup required.
Endpoint Overview
/graphqlUpdate an existing user's account details using their email address. Same functionality as Edit User by ID, but uses email for lookup.
Request Parameters
emailString!RequiredThe email address of the user to update.
resellerUserEdit.passwordStringNew password for the user account.
resellerUserEdit.groupIdIntNew subscription group ID.
resellerUserEdit.multiLoginCountIntMaximum concurrent login sessions.
resellerUserEdit.userProfileEditObjectProfile information to update.
GraphQL Mutation
mutation resellerEditUserByEmail($email: String!, $resellerUserEdit: ResellerUserEdit!) {
resellerEditUserByEmail(email: $email, resellerUserEdit: $resellerUserEdit) {
id
email
username
resellerId
role
enabled
updatedAt
}
}Variables:
{
"email": "customer@example.com",
"resellerUserEdit": {
"password": "NewSecurePass456!",
"multiLoginCount": 3,
"userProfileEdit": {
"firstName": "Jane",
"lastName": "Customer",
"phone": "+1555123456"
}
}
}HTTP Request:
curl -X POST https://api.orbnet.com/graphql \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_RESELLER_TOKEN" \
-d '{
"query": "mutation resellerEditUserByEmail($email: String!, $resellerUserEdit: ResellerUserEdit!) { resellerEditUserByEmail(email: $email, resellerUserEdit: $resellerUserEdit) { id email updatedAt } }",
"variables": {
"email": "customer@example.com",
"resellerUserEdit": {
"multiLoginCount": 3
}
}
}'Response
{
"data": {
"resellerEditUserByEmail": {
"id": "12345",
"email": "customer@example.com",
"username": "janecustomer",
"resellerId": "reseller_789",
"role": "user",
"enabled": true,
"updatedAt": "2024-01-16T14:30:00Z"
}
}
}{
"errors": [
{
"message": "User with email customer@example.com not found or not in your group",
"path": ["resellerEditUserByEmail"],
"extensions": {
"code": "NOT_FOUND"
}
}
],
"data": null
}When to Use
Customer Requests
User contacts you with email only.
Password Resets
Reset password by email address.
Quick Updates
Skip the ID lookup step.
Integration
External systems use email as key.
Best Practices
Verify Email
Confirm email is correct before editing.
Case Sensitivity
Email matching may be case-sensitive.
Notify Changes
Inform user of account updates.
Password Security
Generate strong passwords when resetting.
Related Endpoints
Equivalent Functionality
This endpoint provides the same update capabilities as Edit User by ID, just using email for lookup.
Need User's Full Details?
Look up user information by email before making updates.