Publishing an Event Using the Discovery RFx Publication to External Marketplace API

Use this procedure to publish an event using the Discovery RFx publication to external marketplace API.

Context

Procedure

  1. When a qualified RFx event is created and configured for posting on your site, an event is created and pushed to a message queue specific to your site. Use the /site/{siteId}/events endpoint to retrieve the RFx event from the queue:
    GET {{runtime_url}}/site/{site_id}/events?rsqlfilter=(count=={n};buyer=={buyer_id})
    					
    count
    Optional. Specifies the maximum number of events to return. Default is 1.
    buyer
    Optional. If specified, only events from the specified buyer organization will be returned.
  2. Optional. If any attachments are associated with the RFx event, they will be referenced in the response to your call to the /site/{siteId}/events endpoint. You can pass the attachment CID as a parameter using the /attachment endpoint to download attachment data.
    GET {{runtime_url}}/site/{site_id}/events/{event_id}/attachment/{CID}
                   
  3. Depending whether bidding will take place within SAP Ariba Sourcing or via some other sourcing system, do one of the following:
    • If bidding will take place within SAP Ariba Sourcing, you should remove the message about the event from the queue using the /acknowledge endpoint.

      POST {{runtime_url}}/action/site/{site_id}/events/{event_id}/acknowledge
    • If bidding will not take place within SAP Ariba Sourcing, you need to identify the bidding site URI, using the /events/{eventId} endpoint. Specify the URI in the request body.

      Request URL

      PUT {{runtime_url}}/site/{site_id}/events/{event_id}/rsqlfilter=(ack=={bool})

      Request body

      { "url": "{bidding_site_uri}" }
      ack
      Optional. When this value is true, the request acknowledges the message by removing it from the queue. If false, acknowledgement does not take place, and a subsequent call to the /acknowledge endpoint is necessary
  4. Optionally, you can check the status of the event using the /events endpoint, as follows:
    GET {{runtime_url}}/events?rsqlfilter=(select==”status”;ids==”{comma-separated list of GUIDs}”)
    ids
    A comma-separated list of the unique IDs of the events whose status you seek to check. In most cases, this will be the GUID correspondign to the statusCheckId field in the response body returned from your call to the /site/{siteId}/events endpoint in step 1. This API can accept a maximum of 45 GUIDs in a single call.