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
- 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.
- 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.
- 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
- Under Webhooks, enter the Endpoint URL (HTTPS), choose the events, and press Add webhook. Copy the signing secret; it is shown once.
- 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). - Each delivery is signed with HMAC-SHA256 over the timestamp and body, in the
X-Awra-Signatureheader. Check it before trusting the payload. - 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
- Under Contract prices in the portal (or over the API), the supplier sees the prices agreed on their active contracts.
- 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.
- 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
- Supplier Team, Sessions & Email Preferences
- Supplier Order Acknowledgement & Disputes
- Supplier Contracts & Call-Offs
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.