Deny exhibitor request

The Deny exhibitor request API allows event organizers to reject an exhibitor request submitted for a specific event within their Zoho Backstage portal. Exhibitor requests represent applications from companies or representatives seeking to participate in the event’s expo area.

This endpoint enables you to update the request status to denied and capture the reason for rejection, ensuring clear communication with the exhibitor.

This API is typically used when you want to:

  • Review and reject exhibitor applications during the approval process
  • Maintain control over exhibitor participation in the event
  • Communicate rejection decisions with clear reasoning
  • Ensure accurate exhibitor and booth allocation management

To successfully deny an exhibitor request, you must provide the portal_id, event_id, exhibitorRequestId, and the payload containing the rejection reason.

 

Header

Authorization: Zoho-oauthtoken d92d4xxxxxxxxxxxxx15f52

 

OAuth Scope

zohobackstage.exhibitor.UPDATE

 

Path Parameters

  • portal_id (Long Integer)
    The unique identifier of the Zoho Backstage portal in which the event exists. This ensures that the exhibitor request rejection is performed within the correct portal environment. For example, "portal_id": "31693662" specifies the portal under which the exhibitor request exists.

  • event_id (Long Integer)
    The unique identifier of the event that contains the exhibitor request. This ensures that the denial action is applied to the correct event. For example, "event_id": "3000000000029" specifies the event associated with the request.

  • exhibitorRequestId (Long Integer)
    The unique identifier of the exhibitor request that needs to be denied. This ID uniquely identifies the request submitted by the exhibitor representative. For example, "exhibitorRequestId": "3000000022024" specifies the request that will be rejected.

Payload Parameters

  • reason (String) *
    The reason provided by the event organizer for rejecting the exhibitor request. This value explains why the exhibitor request was denied and may be used for internal tracking or communication with the requester. For example, "reason": "Enter a reason for rejecting this request" indicates the explanation for rejecting the request.

Response Structure and Field Explanations

  • status_code (String)
    The status code returned by the API indicating whether the exhibitor request denial operation was successfully completed. This value represents the outcome of the API request and corresponds to the HTTP response status returned by the server. For example, "status_code": "200" indicates that the exhibitor request was successfully denied.

  • message (String)
    A descriptive message returned by the API confirming the result of the exhibitor request denial operation. For example, "message": "Exhibitor request denied successfully" confirms that the exhibitor request has been rejected and the request status has been updated accordingly.

URL

Copied/backstage/v3/portals/{portal_id}/events/{event_id}/exhibitor_requests/{exhibitorRequestId}/deny

Example

Copied/backstage/v3/portals/{{portal_id}}/events/{{event_id}}/exhibitor_requests/{{exhibitorRequestId}}/deny

Sample Payload

Copied{
  "reason": "Enter a reason for rejecting this request"
}

Sample Response

Copied{
  "status_code": "200",
  "message": "Exhibitor request denied successfully"
}