How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

weclapp Shipment API

Outbound shipments / deliveries.

weclapp Shipment API is one of 7 APIs that weclapp publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Shipment. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://{tenant}.weclapp.com/webapp/api/v1.

6 operations 3 paths 4 schemas 1 DELETE3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://{tenant}.weclapp.com/webapp/api/v1
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

weclapp Shipment API declares 1 security scheme for authenticating requests. An API key is passed in the header as AuthenticationToken (authenticationToken). By default, every request must be authenticated.

  • authenticationToken — API token issued per weclapp user under "My Settings API". Sent in the AuthenticationToken request header. Requests must also send Accept: application/json; PO…

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Shipment 6

Outbound shipments / deliveries.

GET
/shipment
List shipments
getShipments 5 params → 200401
POST
/shipment
Create a shipment
createShipment body → 201400401
GET
/shipment/count
Count shipments
countShipments → 200401
GET
/shipment/id/{id}
Get a shipment
getShipmentById 1 param → 200401404
PUT
/shipment/id/{id}
Update a shipment
updateShipment 1 param body → 200400401404
DELETE
/shipment/id/{id}
Delete a shipment
deleteShipment 1 param → 204401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Shipment (9 properties), ShipmentList (1 property), CountResult (1 property), Error (1 property). Each schema is shown below with its type and property counts.

Error
object
Error envelope (modeled; consult live Swagger for the exact shape).
1 property
CountResult
object
1 property
Shipment
object
Outbound shipment / delivery. Modeled subset of documented fields.
9 properties
ShipmentList
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

weclapp-shipment-api-openapi.yml Raw ↑

Other APIs weclapp publishes across the network.

weclapp Article API
weclapp Customer API
weclapp Purchase Order API
weclapp Quotation API
weclapp Sales Invoice API
weclapp Sales Order API
Where this information came from

This is an independent, third-party profile of weclapp Shipment API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.