- Update payout method
Create or update the user's preferred payout method. The request must always include receiver_wallet. For PAYPAL and VENMO the client must also supply receiver (an email or phone respectively). For BILL_CREDITS the receiver must not be supplied — it is derived server-side from the user's linked billing account.
- Mock serverhttps://developers.ev.energy/_mock/ev.energy-api-v2/users/{user_id}/payout_method
- Live API for both production and sandbox requests.https://api.ev.energy/v2/users/{user_id}/payout_method
- Staging server for internal testing only.https://api-staging.ev.energy/v2/users/{user_id}/payout_method
curl -i -X PATCH \
'https://developers.ev.energy/_mock/ev.energy-api-v2/users/{user_id}/payout_method' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'EvEnergy-Version: 2' \
-d '{
"receiver": "alice@example.com",
"receiver_wallet": "PAYPAL"
}'Payout method updated successfully.
Indicates the version of the API that generated this response. If EvEnergy-Version was not specified in the request, this will be your OAuth application's default version.
The maximum number of requests that can be made to this endpoint per hour. Defaults to 1000 but may vary per client.
The destination identifier for the payout (email for PAYPAL, phone for VENMO, billing account number for BILL_CREDITS). Null when no payout method has been set up.
The semantic type of the receiver field. Server-derived.
{ "url": "https://api.ev.energy/v2/users/user01HN2NJ9NMRZBXT1H6FT9N7735/payout_method", "receiver": "alice@example.com", "receiver_type": "EMAIL", "receiver_wallet": "PAYPAL" }