Welcome to the Pabliq API!This documentation provides information about the endpoints for retrieving procurements and their associated files that match your saved searches configured in the Pabliq UI.Fetching procurements via the API is available only to enterprise plan customers with a data plan. You can easily check if you have an enterprise plan by looking next to our logo in the top menu.All customers can always use Pabliq’s UI. Please note that marking hits as read in the Pabliq UI does not affect the API response, as we treat the inbox as a UI feature and API hits as a separate feature.Understanding Saved Searches#
In most views within the Pabliq UI, the content displayed to you is already filtered based on your defined saved searches. These saved search criteria can include keywords, CPV codes, NUTS codes, and procurers. You can easily modify your saved searches in the Pabliq App to suit your needs.When fetching hits via this API, you are retrieving new or updated procurements that match your saved searches (that has API turned on). In the response, hitInfo specifies which saved searches generated the hit. This can be particularly useful for larger organizations to assign different hits to different teams based on the relevant saved search.In the Saved Searches view, you have the option to toggle whether the results of a saved search can be accessed via the API.Setting up optimal saved searches may be more complex than it seems. We recommend not combining keywords with CPV codes in a single search. Instead, create two separate saved searches—one with keywords and another with CPV codes. Our onboarding team and support staff are available to assist you with this process.
Recommended Processes for Fetching Procurement Hits#
As always, when designing new features, we strive to be as user-centric as possible. Therefore, we offer two different solutions for fetching your procurement hits.1.
Managed by Pabliq:
In this solution, Pabliq keeps track of which hits you have already fetched and returns only unfetched or updated hits. We recommend fetching new hits once a day, although you can fetch as frequently as every 30 minutes. If you need to retrieve already fetched hits, you can do so by adjusting the query parameters.
2.
Managed by the Customer:
In this solution, the customer is responsible for keeping track of when and for which intervals they have fetched hits. There is no risk in refetching hits, as each hit includes a unique pabliqId along with createdUtc and lastUpdatedUtc timestamps.
