Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Path Parameters
Body
application/json
The user information to create
Response
User was updated
The updated user
curl --request PUT \
--url https://app.pennylane.com/api/external/v2/users/{id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"user": {
"email": "[email protected]"
}
}'
{
"user": {
"id": 123,
"email": "[email protected]",
"created_at": "2021-01-01T00:00:00Z",
"updated_at": "2021-01-01T00:00:00Z"
}
}
Updates an existing user. In order to authenticate the request, a valid OAuth2 token must be provided. The token must have the users:update_email
scope and be generated by a user via the authorization_code
grant type.
ℹ️ This endpoint requires one of the following scopes:
users
,users:update_email
curl --request PUT \
--url https://app.pennylane.com/api/external/v2/users/{id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"user": {
"email": "[email protected]"
}
}'
{
"user": {
"id": 123,
"email": "[email protected]",
"created_at": "2021-01-01T00:00:00Z",
"updated_at": "2021-01-01T00:00:00Z"
}
}
The access token received from the authorization server in the OAuth 2.0 flow.
The user information to create
Show child attributes
User was updated
The updated user
Show child attributes
Was this page helpful?