Developer DocumentationLegacy APICvent Supplier Network APIUser Guide for SuppliersSubmitting Additional Types of RFP Responses Through the API

Turn Down an RFP

Indicate to a planner you are choosing not to bid on an RFP.

Supported Methods

POST. Turns down the RFP for the specified supplier and RFP.

PUT. Updates a previously submitted Turn Down message with new reason and/or comment information.

Request POST

https://api.cvent.com/rfp-response/v1/rfp/<rfpId>/supplier/<supplierId>/turndown

Response Codes

CodeResponse
200Request completed successfully
403An application without the required permissions has attempted to create a proposal for the RFP and Supplier ID combination
404An RFP or supplier with the specified rfpId or supplierId was not found

Request Body Type

application/json

Request Body Schema

Response-Post/turndown.json

Validations

  • responseReason and additionalReason cannot both be null
  • if using additionalReason, the value must be set to VENUE_PERMANENTLY_CLOSED or VENUE_TEMPORARILY_CLOSED
  • responseReason must be set to one of the following values if specified:
    • TOO_SPACE_INTENSIVE
    • ROOMS_TO_SPACE_RATIO
    • LOW_BUDGET
    • NO_FOOD_AND_BEVERAGE
    • MEETING_SPACE_UNAVAILABLE
    • DATES_OR_PATTERN
    • SLEEPING_ROOMS_UNAVAILABLE
    • COMPETITOR_CONTRACT_AGREEMENT
    • RENOVATIONS
    • OTHER
    • REQUESTED_ROOM_RATE_TOO_LOW
    • FOOD_AND_BEVERAGE_TOO_LOW
    • VENUE_TOO_SMALL
  • If responseReason is set to OTHER, comment must be provided
  • If provided, emailAddress must be in a valid format

Forwarding RFPs

The Cvent application allows one supplier to forward an RFP they have received to one or more other suppliers (provided the planner has allowed forwarding on their RFP) if they feel the other suppliers could better accommodate the event or group the RFP represents.

POST Request

http://api.cvent.com/rfp/v1/supplier/rfp/{rfp-id}/rfpForward

Request Body Type

application/json

Request Body Schema

Response-Post/rfpForward.json

Notes

  • forwarderSupplierId is the Cvent supplierId of the supplier you want to forward the RFP from
  • targetSupplierIds is an array of Cvent supplierIds you want to forward the RFP to
  • isForwardable must be set by the planner to true in the RFP you are trying to forward for the forward to succeed

Response

The response to a successful forward of an RFP to a supplier is indicated in the message. Any validation or business rule like the RFP not being forwardable or the supplier forwarding the RFP did not receive the RFP will return error message with the appropriate reason as applicable.

Response Codes

CodeResponse
200Request completed successfully
403An application without the required permissions has attempted to create a proposal for the RFP and Supplier ID combination
404An RFP or supplier with the specified rfpId or supplierId was not found
Last updated on