weclapp Cloud ERP

weclapp is a cloud ERP for small and mid-sized companies. This connector reads and writes weclapp through the REST API v2: parties (customers, suppliers, contact persons, leads), quotations, sales orders, sales invoices, articles and stock, purchase orders, tasks, comments and time records. Recurring invoices and opportunities are read-only.

Getting credentials

1. In weclapp, open your user menu → My settings → API and copy the API token into WECLAPP_API_TOKEN. Each user has one token; generating a new one invalidates the old one.
2. Set WECLAPP_TENANT to the first part of your weclapp address only: for acme.weclapp.com, enter acme. Requests go to https://acme.weclapp.com/webapp/api/v2 with the token in the AuthenticationToken header.

Permissions follow the user: the token acts as the weclapp user it belongs to, so records that user's role cannot see are missing from the results. Use a user with read access to sales, CRM and articles, and write access to whatever the AI should change. A write the user's role does not allow answers 403.

Finding records: get tools take the internal id, a numeric string such as "3346", not the document number. To find a document by its number, filter the list tool: orderNumber-eq=SO-1042, invoiceNumber-eq=RE-1042, quotationNumber-eq=AN-1042, articleNumber-eq=A5101. Customers and suppliers both live under /party: filter with customer-eq=true or supplier-eq=true.

Filter syntax: filter is sent as query parameters written property-operator=value and joined with &, e.g. paymentStatus-eq=OPEN&dueDate-lt=1767225600000. Operators: eq, ne, lt, gt, le, ge, like, ilike, in, notin, null, notnull. -null and -notnull take an empty value (customerNumber-notnull=); -in takes a bracketed list. A property name that does not exist returns HTTP 400, in filter and in properties alike. Sales documents have no customerName: the name is in recordAddress, the link is customerId.

Data formats: dates are Unix epoch milliseconds, in responses and in filters (2026-01-01 00:00 UTC is 1767225600000). Prices and quantities come back as decimal strings such as "119.00". Unpaid invoices are paymentStatus-eq=OPEN, cancelled ones status-eq=CANCELLED, credit notes salesInvoiceType-eq=CREDIT_NOTE: leave credit notes out when adding up revenue.

Pagination and limits: page starts at 1; pageSize defaults to 100 and is capped at 1000. Fetch the next page until a page returns fewer rows than pageSize. Leave properties empty: every field comes back, and a guessed field name fails the whole call with 400 "unknown property". When a list must be trimmed, use only the field names listed in that tool's properties description. weclapp has no fixed rate limit, but it queues requests under heavy load and answers HTTP 429 after 30 seconds in the queue: wait, then retry.

Recurring invoices: /recurringInvoice is not part of weclapp's published OpenAPI file. If weclapp_list_recurring_invoices returns 404 on a tenant, the resource is not available there; invoices generated from a recurring invoice still carry its recurringInvoiceId.

Writing to weclapp: every write tool changes the live ERP. Read the record first, tell the user what will change, and wait for their confirmation. The delete tools are installed switched off. If a write tool named here is missing, the connector was set up before it existed: ask the user to apply the connector update in AnythingMCP.

• Partial updates: the weclapp_edit_* tools send PUT with ignoreMissingProperties=true, weclapp's documented way to change single fields, so fields you leave out keep their values. Send only what changes: read-only fields such as createdDate, statusHistory or amounts are refused with HTTP 400 ("property ... is read-only"), so never copy a whole record back.
• Lists are replaced, not merged: when you send addresses, contacts, partyEmailAddresses, orderItems, quotationItems or articlePrices, include every entry to keep by its id (the id alone keeps it unchanged) and new entries without an id. An entry you leave out is deleted.
• Optimistic locking: pass the record's version from your last read and weclapp refuses the change with HTTP 409 "optimistic lock error" if someone changed it meanwhile; read again and retry. Without version the check is skipped.
• dryRun: true on create, edit and delete tools makes weclapp validate the request and answer without saving.
• References are ids (customerId, responsibleUserId, unitId, warehouseId...). weclapp_list_reference_data lists users, warehouses, storage places, units, taxes, currencies, payment terms and the other lists those ids point to.
• Decimals are sent as strings ("quantity": "2", "unitPrice": "119.00") and dates as epoch milliseconds. A position with your own price needs manualUnitPrice: true next to unitPrice.
• Status changes: weclapp_set_sales_order_status sends the status alone (weclapp refuses a reopen combined with other changes), weclapp_cancel_sales_order cancels or closes an order, weclapp_set_quotation_status uses weclapp's quotation status action. weclapp_invoice_sales_order creates a draft invoice from an order; every call creates another one.
• Single-field shortcuts: weclapp_set_sales_invoice_responsible, weclapp_set_sales_order_responsible and weclapp_set_party_responsible change only the responsible user. They do the same as the weclapp_edit_* tools with {"responsibleUserId": ...}, with less room for a wrong body.
• Purchasing master data: weclapp_add_supply_source (supplier + purchase price for an article), weclapp_add_manufacturer and weclapp_add_article_item_group create records that articles and documents then reference by id.
• Stock is changed by bookings (weclapp_book_stock_in, weclapp_book_stock_out), not by editing the article; they take effect at once.

Cloud reachability: *.weclapp.com is publicly reachable over HTTPS.