Skip to main content

User Parameters

User parameters define end-user account information, contact details, and metadata for the Podero platform.
Use the external_user_id field to link Podero users with your internal customer management system.

Required Parameters

string (UUID)
required
Organization ID that the user belongs to. Assigned during partner onboarding.Example: 016b78a7-0c7c-4241-a277-015c3ad3cb90Writable: No (set at creation, cannot be changed)
string
required
User’s email address. Must be unique within the organization.Example: [email protected]Writable: Yes
enum
required
User’s access level within the organization.Options:
  • admin - Full access to all organization resources
  • staff - Can manage end-users and devices, but not other staff/admins
  • user - End-user with access only to their own resources
Example: userWritable: Yes (admin only can change roles)

Optional Parameters

Personal Information

string
Partner’s internal user identifier for cross-referencing with your systems.Example: 134681893870Writable: Yes
string
User’s first name.Example: PeterWritable: Yes
string
User’s last name.Example: SchmidtWritable: Yes

Address Information

string
Primary street address with house number.Example: Platz der Republik 1Writable: Yes
string
Additional address information (apartment number, floor, building, etc.).Example: Apt 4BWritable: Yes
string
Postal/ZIP code.Example: 11011Writable: Yes
string
City or town name.Example: BerlinWritable: Yes
string
Country code in ISO 3166-1 alpha-2 format.Example: DEWritable: Yes

Location Coordinates

Latitude and longitude can be used for location-based optimization and regional pricing.
float
Geographic latitude coordinate.Example: 40.7128Writable: Yes
float
Geographic longitude coordinate.Example: 74.0060Writable: Yes

Usage Examples

Create User with Minimum Required Fields

Create User with Complete Information

Update User Information

Best Practices

  • Always set external_user_id to link with your internal systems
  • Use a consistent ID format across all users
  • This makes it easy to sync data between systems
  • Useful for customer support and troubleshooting
  • Collect user names and addresses for better optimization
  • Location data helps with regional pricing and weather-based optimization
  • Keep email addresses up-to-date for important notifications
  • Validate email format before sending to API
  • Use user role for end-customers
  • Use staff role for support team members
  • Reserve admin role for managers and senior staff
  • Only admins can change user roles
  • Only collect data you need and have permission to store
  • Follow GDPR and other privacy regulations
  • Provide users with access to their own data
  • Implement data retention policies

Getting Started

Create your first user

User Management

Back-office user workflows

Team Administration

Manage staff and admin users