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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
weclapp

weclapp Purchase Order API

Purchase orders to suppliers.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Purchase Order. 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 5 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 5 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
weclapp
Resource Areas
1

Authentication & Security 1

weclapp Purchase Order 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.

Purchase Order 6

Purchase orders to suppliers.

GET
/purchaseOrder
List purchase orders
getPurchaseOrders 5 params → 200401
POST
/purchaseOrder
Create a purchase order
createPurchaseOrder body → 201400401
GET
/purchaseOrder/count
Count purchase orders
countPurchaseOrders → 200401
GET
/purchaseOrder/id/{id}
Get a purchase order
getPurchaseOrderById 1 param → 200401404
PUT
/purchaseOrder/id/{id}
Update a purchase order
updatePurchaseOrder 1 param body → 200400401404
DELETE
/purchaseOrder/id/{id}
Delete a purchase order
deletePurchaseOrder 1 param → 204401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are PurchaseOrder (9 properties), OrderItem (6 properties), PurchaseOrderList (1 property), CountResult (1 property). Each schema is shown below with its type and property counts.

OrderItem
object
A line item on an order, quotation, or invoice. Modeled subset.
6 properties
Error
object
Error envelope (modeled; consult live Swagger for the exact shape).
1 property
CountResult
object
1 property
PurchaseOrder
object
Purchase order to a supplier. Modeled subset of documented fields.
9 properties
PurchaseOrderList
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

weclapp-purchase-order-api-openapi.yml Raw ↑

Other APIs weclapp publishes across the network.

weclapp Article API
AE Profile APIs.io
weclapp Customer API
AE Profile APIs.io
weclapp Quotation API
AE Profile APIs.io
weclapp Sales Invoice API
AE Profile APIs.io
weclapp Sales Order API
AE Profile APIs.io
weclapp Shipment API
AE Profile APIs.io
#Purchase Order
← Back to W APIs
API Details
ID
weclapp:weclapp-purchase-order-api
Base URL
https://{tenant}.weclapp.com/webapp/api/v1
Docs
https://www.weclapp.com/api/
Provider
weclapp
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=weclapp-purchase-order-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/weclapp-purchase-order-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of weclapp Purchase Order 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.