Download the PHP package geccomedia/weclapp without Composer

Laravel Weclapp

This repo implements most of the Laravel Eloquent Model for the Weclapp web api.

Contents

• Installation
• Usage
• Available Models
• Custom Models
• Mass Assignments
• Relations
  • Eager loading
  • Lazy loading
  • Inverse relations
• Additional Properties
• Custom Actions
  • Collection-level actions
  • Instance-level actions
• Read-only Models
• Embedded Sub-Objects
• Sub Entities
• Error Handling
• Logging
• Party-type Models
  • leadStatus values
• Boolean Filters
• System & Job Utility APIs
  • SystemApi
  • JobApi
• License & Copyright

Installation

Require this package with Composer

Add the variables to your .env:

Usage

Use existing models from the Geccomedia\Weclapp\Models namespace.

Most Eloquent methods are implemented within the limitations of the web API.

Available Models

Over 150 models are provided, covering all queryable Weclapp API endpoints — including SalesOrder, Customer, Article, Shipment, PurchaseOrder, Invoice, Ticket, and many more. Every model has full @property annotations for IDE autocompletion.

Custom Models

The API route is derived automatically from the class name using lcfirst(ClassName), so SalesOrder maps to salesOrder, Article maps to article, etc. You only need to declare $table when your class name does not match the API route:

Mass Assignments

If you want to do mass assignment please use unguard and reguard:

Relations

Models declare belongsTo and hasMany relationships using Weclapp's camelCase foreign key convention (e.g. customerId, not customer_id).

Eager loading (recommended — single batched request)

Use with() to load related models in one extra request instead of one per record:

Lazy loading (N+1)

Without with(), each relation access fires its own HTTP request:

Inverse relations (hasMany)

Common inverse relations are defined, so you can traverse from either side:

Additional Properties

Weclapp can return extra computed fields that are not included by default. Request them with withProperties():

This can be combined with select() and other query methods:

Custom Actions

Weclapp exposes many action endpoints beyond standard CRUD. Call them via action() at the class level or callAction() on a model instance.

Collection-level actions

Instance-level actions

All actions return the decoded JSON response body as an array, or null if the response has no body.

Read-only Models

Some Weclapp endpoints are read-only (no create or delete). Attempting to save() a new instance or delete() an existing one on these models will throw a NotSupportedException immediately, without making an HTTP request.

Mutation restrictions are expressed via three composable traits:

IsReadOnly (use NoCreate, NoUpdate, NoDelete) and IsUpdatableOnly (use NoCreate, NoDelete) are convenience aliases for common combinations.

Embedded Sub-Objects

Weclapp embeds related data directly in API responses rather than using separate endpoints. These are automatically hydrated into typed SubModel value objects on read.

toArray() and toJson() always return plain nested arrays, so serialisation and API writes are unaffected.

Sub Entities

Weclapp treats some models as sub-entities that belong to a parent. For these, supply the parent entity with whereEntity($name, $id):

Without the call to whereEntity the API will return an error. See #22 for more information.

Error Handling

Every failed HTTP call (4xx or 5xx response) throws Geccomedia\Weclapp\WeclappApiException.

WeclappApiException extends \RuntimeException. It intentionally does not implement PSR-18's Psr\Http\Client\RequestExceptionInterface, which is on Laravel's internal suppression list (internalDontReport). Had we wrapped or re-thrown Guzzle's own RequestException directly, Laravel would silently discard it and nothing would appear in your logs. WeclappApiException is reported normally by Laravel's exception handler, including in queue jobs.

Logging

To inspect the HTTP requests being made, enable the connection query log:

Party-type Models

Weclapp stores customers, suppliers, leads, and contacts all as records in the single /party endpoint, differentiated by boolean role flags and a leadStatus field. The four convenience model classes each apply a global query scope so they automatically filter to the right subset:

The scopes are transparent — any extra where() clauses stack alongside them:

A single weclapp party can carry multiple roles simultaneously (e.g. customer = true and supplier = true). Party::all() returns every party record unfiltered when you need to query across roles.

leadStatus values

Boolean Filters

PHP true and false values passed to where() or whereIn() are automatically serialised to the strings "true" and "false" that the weclapp API expects:

System & Job Utility APIs

Weclapp exposes a handful of endpoints under /system and /job that have no CRUD model. Two dedicated classes wrap these as typed methods.

SystemApi

JobApi

Weclapp runs long-running background jobs asynchronously. Use JobApi to poll or cancel them by type.

Valid type values are the SCREAMING_SNAKE_CASE job names from the Weclapp API spec (e.g. INVENTORY_BOOKING, MATERIAL_PLANNING_RUN, MASS_SHIPMENT_CREATION, ACCOUNTING_EXPORT, and many more).

License & Copyright

Copyright © 2017–2026 Gecco Media GmbH

License