AWRA OpsHub Search

AWRA Help Center

Copy link
Procurement Approvals Suppliers
01 Procurement Module Guides 02 Request to PO Step-by-Step Workflows 03 Vendor Portal Module Guides

Supplier API & Webhooks

Larger suppliers connect their own ERP or warehouse system: submit quotations, acknowledgements, shipment notices, invoices and price proposals over the API, and receive signed events by webhook.

Everything is set up in the supplier portal under Integrations (/vendor/integrations), which also carries the full API reference. Base path: /api/supplier/v1. Setting up tokens and webhooks is on the web portal.

API Tokens

  1. Under API tokens, enter a Token name, such as SAP Business One — production, and choose an expiry: never, or in 30, 90 or 180 days or a year.
  2. Tick the scopes it may use: read RFQ invitations, submit quotations, read purchase orders, acknowledge orders and post on their thread, send shipment notices, submit invoices, propose contract prices.
  3. Press Create token and Copy it now. It is shown once and stored only as a hash.
  • Send it as a bearer token. A request acts as the contact who created the token, limited to its scopes — it can never do more than that contact could.
  • If that contact’s access is removed, or the company’s account is switched off, the token stops working.
  • Limits: 60 requests a minute and 1,500 an hour per token; over that you get a 429 with a Retry-After header.
  • Revoke a token from Integrations or from Sign-in & sessions.

Webhooks

  1. Under Webhooks, enter the Endpoint URL (HTTPS), choose the events, and press Add webhook. Copy the signing secret; it is shown once.
  2. Events: an RFQ invitation (rfq.invited), a purchase order issued (po.issued), a purchase order changed when a change order is approved (po.changed), and a payment made (payment.made).
  3. Each delivery is signed with HMAC-SHA256 over the timestamp and body, in the X-Awra-Signature header. Check it before trusting the payload.
  4. Press Test to send a sample.
  • If your endpoint does not answer with a 2xx, we retry for about four hours. After 25 failures in a row the webhook is switched off.
  • The Delivery log lists every event we sent, newest first, with its delivery id, attempts and response.
  • The address must be a public HTTPS address, and it is checked again on every send.

Contract Price Proposals

  1. Under Contract prices in the portal (or over the API), the supplier sees the prices agreed on their active contracts.
  2. They enter a New price, the date it applies From, a lead time if it changes, and a Reason, such as Steel surcharge from 1 November, and press Propose price.
  3. The buyer reviews it under Supplier price proposals, reached from Supplier contracts, and presses Approve or Decline with a note. Only approval changes the contract’s price and lead time.

Buyers can approve proposals on the web or in the AWRA mobile app. Approving needs the permission to edit vendors.

Related

Need help with this topic?

Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.

Open support guide