Users

User Management Overview

User management in Drive API is designed to be simple and flexible. The only required information is a unique user ID, which should match the identifier used in your own system. This allows for seamless integration between your user management system and Drive API.

Key Concepts

• All Users have a unique ID that comes from your system
• Email addresses are optional but must be unique if provided
• Users can be deleted only if they have no outstanding debt

Creating Users

API Reference

When creating a new user:

• Only the id field is required (any string is accepted) when you are the Merchant on Record. If Plugsurfing is the Merchant on Record the email field is mandatory as well.
• Use the same user ID from your system for consistency
• Optionally provide an email address
• Ensure the ID is unique to avoid conflicts

Managing Users

API Reference for Get User

API Reference for Update User

With these endpoints, you can:

• Retrieve user details including debt status
• Update user email addresses. Note: two users can't have the same email. If a request is made to update an user's email with one that is already used, we will reject it with a 409 http code.
• Delete users when they no longer need access

Deleting Users

API Reference

Disables all charging keys of the user immediately and schedules the user's deletion for 30 days later. This delay ensures that late-arriving Charging Detail Records (CDRs) can still be linked to the user.

Notes:

• If Plugsurfing handles payments, users with outstanding debt cannot be deleted.
• We reserve the right to reject this call if less than 3 years passed since recent user activity, due to legal obligation of storing data.