Skip to main content
curl -X POST https://api.hellotracks.com/api/createaccount \
  --header 'API-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  -d '{
    "data": {
      "name": "Jane Smith",
      "username": "jane@company.com",
      "phone": "+14155559999"
    }
  }'
Create a new member (user) in your organization. This endpoint handles account creation, role assignment, and automatic invitation delivery via email or SMS.

REQUEST

POST https://api.hellotracks.com/api/createaccount

{
   "data": {
      "name": "John Doe",
      "username": "johndoe@company.com",
      "password": "secretpassword123",
      "role": "worker",
      "phone": "+14155551234"
   }
}
name
string
required
Full name of the user. Required.Example: "John Doe", "Sarah Johnson"
username
string
required
Username for login, typically an email address. Required.Must be unique across the platform. If this username already exists in your company, the existing member will be reactivated instead of creating a duplicate.Example: "worker@company.com"
password
string
Initial password for the account. Optional.
  • If provided: Member can log in immediately with this password
  • If omitted: Member receives an invitation via email or SMS to set their own password
Recommendation: Leave empty and let users set their own password for better security.
role
string
default:"worker"
Role determines the user’s permissions. Optional, defaults to “worker”.Available roles:
  • "worker" - Field worker with basic permissions (default)
  • "operator" or "dispatcher" - Dispatcher with management capabilities
  • "administrator" or "admin" - Full administrative access
See Member Object - Role & Permissions for details.
phone
string
Phone number for the user. Optional.Used for SMS invitations (if password not set) and contact purposes.Format: Include country code, e.g., "+14155551234"

Account Reactivation

If you create a member with a username that already exists and was previously part of your company:
  • The existing account will be reactivated instead of creating a new one
  • Previous data and history are preserved
  • The member is automatically re-added to your organization
This prevents duplicate accounts and maintains continuity.

Automatic Invitation

After creating a member:
  • If password was not provided: An invitation is automatically sent via email (if email username) or SMS (if phone provided)
  • The invitation allows the new member to set their own password and complete onboarding
  • Company members list is automatically updated via push notifications

Permissions

  • Only administrators and company owners can create new members
  • Workers and dispatchers cannot create accounts

RESPONSE

{
  "status": 0,
  "uid": "abc123",
  "account": {
    "uid": "abc123",
    "username": "johndoe@company.com",
    "name": "John Doe",
    "phone": "+14155551234",
    "role": "worker",
    "teams": [],
    // ... complete member object
  }
}
status
integer
required
Status code. 0 indicates success.
uid
string
required
Unique identifier of the newly created (or reactivated) member. Use this UID for subsequent API calls.
account
object
required
Complete member object with all properties initialized. See the Member API Object for full structure.

Examples

curl -X POST https://api.hellotracks.com/api/createaccount \
  --header 'API-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  -d '{
    "data": {
      "name": "Jane Smith",
      "username": "jane@company.com",
      "phone": "+14155559999"
    }
  }'
Complete Field Reference: See the Member API Object for documentation of all properties in the returned member object.
Best Practice: Don’t set the password field. Let new members receive an invitation and set their own password for better security and user experience.
I