Webhooks Overview

Webhooks let Tendium push data to your systems automatically — no polling required. When an event happens in Tendium (such as a bid being created or updated), a notification is sent to a URL you specify.

Think of it like mobile notifications: when something important happens, you get a ping. You can then decide how to handle it.

How does the solution work?

A webhook sends information only when specific events occur, known as a trigger. In Tendium there are two triggers:

Event	When it is sent
Bid created	A bid is created — by dragging a Tender or Call-Off into a bidflow, or by creating the bid manually.
Bid updated	An existing bid changes in Tendium — a field is edited, the stage changes, someone is assigned, or a manual document is added or removed.

When this happens, a notification is sent via the webhook to a location of your choice. The service you use receives, retrieves, and forwards information to your CRM system (or another target).

Note

Each webhook is registered for one event type, with its own endpoint URL and its own secret. To receive both events, create two webhooks.

The notification itself is small — it tells you which bid changed, not what the new values are. Your service then fetches the current bid data from Tendium’s API. See the Setup guide for the technical detail.

Compatible systems

Webhooks are a flexible solution that can integrate with many systems, including:

• Microsoft Dynamics
• Salesforce
• Lime
• Upsales
• HubSpot
• Or any other CRM / receiving system

If you have systems apart from CRM where you consistently move procurement or bid information, it might be possible to integrate with those as well — contact Tendium to discuss your specific needs.

What data is available?

Procurement data

• Unique Tendium bid ID
• Tender / bid title and description
• Buyer name, buyer ID, and buyer contact email
• Submission deadline and question deadline
• Publication date, and when the procurement data was last updated
• Contract duration (number and unit)
• Bid type (call-off, procurement, or manually created bid)
• Estimated contract value
• Whether the procurement is a framework agreement
• CPV codes and procurement status
• Link for submission
• The bid’s stage in Tendium
• The bidflow the bid belongs to
• Assigned person
• Custom bid field data

Procurement documents

• List of associated files, both public procurement documents and files uploaded to the platform
• The date each file was added, so you can spot newly published documents
• Signed URLs for fetching them

Caution

File URLs are time limited, and the countdown starts when you fetch the bid data — not when the webhook was sent. Public procurement files expire after 24 hours; files uploaded to the platform expire after 12 hours.

Example scenarios

1. You find a procurement in Tendium or receive a request in your inbox.
2. You move it to a bidflow — or create a manual bid in a bidflow.
3. The bid information is sent to your CRM or another recipient system, either automatically or on-demand.
4. Someone later edits the bid in Tendium — a bid updated event lets your CRM pick up the new state.

Note

Changes published by the buyer — a moved deadline, a changed status, or newly published tender documents — do not currently send an update event. If your integration must stay accurate, re-fetch the bids you care about periodically in addition to consuming webhooks.

Inside the bidflow

Once your webhook is set up, you will see a new setting in your bidflows. From this setting, you can decide whether bids created in the bidflow (by dragging in a procurement or a call-off, or manually) will automatically send information to your CRM — or if you prefer to send it on-demand.

The setting is stored per webhook, so if you have one webhook for each event type, you can make bid created automatic while keeping bid updated on-demand, or the other way around. When you have not made a choice for a bidflow, webhooks are sent automatically.

Webhook statuses

Statuses are visible both in the overview view of a bidflow and in the preview of a bid card:

Color	Meaning
Green	Information has been successfully received by your system.
Yellow	Tendium successfully sent the information, but we are unsure if your system received it.
Red	Either we failed to send the information, or your system failed to receive it.
Blue	Information has not yet been sent. Can also be used to resend.

Note

You can always change the status manually if needed. It is also possible to resend the information. Be aware that resending may result in duplicates in your receiving system unless you have a way to manage this.

The status shown on the bid reflects the bid created event. Statuses reported for bid updated deliveries are recorded but not displayed there.

Setup steps at a glance

1. Set up a service that can receive, retrieve, and forward information on your side.
2. Create a webhook in Tendium for each event you want to receive.
3. Create an integration token in Tendium.
4. Start receiving and fetching information from Tendium — “listen” to your webhook.
5. Map fields from Tendium to the corresponding ones in your system.
6. Set the appropriate statuses in Tendium.

Ready to get started? Head to the Setup guide for the full technical walkthrough.