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 Types
  4. Event Payloads

Company Staff Events

Company Staff Events are triggered by certain actions aimed at the company’s employees (staff).

company.staff.added – occurs when the Company adds a Staff user to itself. The staff user must be registered, not only invited (Listing 5.5).

Listing 5.5 – Example of company.staff.added Payload (JSON)

{
    "type":      "company.staff.added",
    "data":      {
        "user":     {...//User Model}
    },
    "created_at":  {...//Date Time Model}
}

company.staff.deleted – occurs when Company deletes its own Staff user. The user must be registered, not only invited (Listing 5.6).

Listing 5.6 – Example of company.staff.deleted Payload (JSON)

{
    "type":      "company.staff.deleted",
    "data":      {
        "user":     {...//User Model}
    },
    "created_at":  {...//Date Time Model}
}

company.staff.updated – occurs when certain data is updated in an company’s Staff user, such as a name or email, for example (Listing 5.7).

Listing 5.7 – Example of company.staff.updated Payload (JSON)

{
    "type":      "company.staff.updated",
    "data":      {
        "user":     {...//User Model}
    },
    "created_at":  {...//Date Time Model}
}
PreviousCompany EventsNextEnd User Events

Last updated 8 months ago