FAQ for Organization
  • Welcome
  • Onboarding Guide
    • Mandatory settings
      • 1. Integrate your Telecoms
      • 2. Create Company
      • 3. Upload your SIM(s)
      • 4. Create Plan(s)
      • 5. Assign the plan to SIM(s)
    • Optional settings
      • 1. Account Settings
      • 2. User Profile
      • 3. PSP Integration
      • 4. Invoice Integration
      • 5. Create Pools
      • 6. Invite Staff
      • 7. Customize Columns
      • 8. Notifications
      • 9. Communication
  • Menu
    • Roles on the platform
    • SIMs
      • SIM Statuses
      • General Terms
      • Key Features
      • Q&A
    • Satellite
      • Terminal Statuses
      • Upload Terminals
    • Pools
    • Plans
      • Prepaid
      • Subscription
      • PAYGO
    • Companies
    • End Users
    • Automation - Rules
    • Transactions
    • Wallet
    • Webhooks
      • Terms used
      • Endpoint validation
      • Authentication
      • Webhook Payload Models
        • Account Model
        • End User Model
        • Account Address Model
        • Wallet Model
        • Plan Model
        • Pool Model
        • SIM Card Model
        • Status Model
        • User Model
        • Prepaid Refill Model
        • Date Time Model
        • Rule Model
        • Payment Model
        • Credit Card Model
      • Webhook Payload Types
        • Technical Payloads
        • Event Payloads
          • Company Events
          • Company Staff Events
          • End User Events
          • SIM Card Events
          • Payment Payloads
        • Rule Payloads
          • SIM Card Rule Payloads
          • SIM Pools Payloads
          • Wallet Payloads
  • e-SIM Store
    • Upload SIMs
    • eSIM Purchase & Activation
    • eSIM Store Activation
    • Q&A
Powered by GitBook
On this page
  1. Menu
  2. Webhooks
  3. Webhook Payload Models

User Model

The User Model – is a base model for showing platform user parameters. Models fields are presented in the table (Table 4.13), with an example below (Listing 4.9).

Table 4.13 – Fields of User Model

№
Key
Type
Exists
Description

1

uuid

uuid v4, string

required

Main identifier of user

2

email

string

required

User email

3

first_name

string

optional

User first name, if it set

4

last_name

string

optional

User last name, if it set

5

status

Status Model

optional

Current user status

6

company

Account Model

optional

If End User does not exist

7

end_user

End User Model

optional

Main account for user

8

is_two_factor_enabled

boolean

optional

Shows user 2FA state

9

timezone

string

optional

Shows user setting timezone

10

format_date_time

string

optional

User format for date and time

11

format_number

string

optional

User format for numbers

Listing 4.9 – Example of User Model (JSON)

{
    "uuid":                    "b528bcb9-86cf-2d72834d02ab",
    "email":                   "user_email@gmail.com",
    "first_name":              "John",
    "last_name":               "Johnson",
    "status":                  {...//Status Model},
    "company":                 {...//Account Model},
    "end_user":                {...//End User Model},
    "is_two_factor_enabled":   true,
    "timezone":                "UTC",
    "format_date_time":        "Y-m-d H:i:s",
    "format_number":           "fr-CA"
}

PreviousStatus ModelNextPrepaid Refill Model

Last updated 8 months ago