Skip to main content
All CollectionsDashboardActivity
How to Use the Requests Table
How to Use the Requests Table

Access a comprehensive log of API requests.

Lucia Burin Sestakova avatar
Written by Lucia Burin Sestakova
Updated over 2 months ago

πŸ” Required Role Permissions: Requests

πŸ”“ Optional Role Permissions: Save Searches, See Bulk Action

The Requests table records every request made to the API, along with the responses received. API logs play a crucial role in maintaining and troubleshooting interactions with API-connected partners.

Having access to these logs is incredibly useful as it helps Ventrata diagnose problems, ensuring faster resolution times. By default, you can view the following details in the log:

  • Request timestamps

  • Request URLs

  • HTTP methods used (GET, POST, etc.)

  • Status codes of responses

  • Response times

  • Error messages, if any

Default Columns

  • Service

  • Action

  • Subrequest

  • IP Address

  • HTTP Method

  • Path

  • Response Code - a 3-digit number that states the server's response

  • Duration

  • Request Date

  • Request Time

Actions

The action bar between the navigation bar and the bookings table enables you to perform a number of additional functions.

  • Search bar - filter the bookings table, using any parameter from the available columns

  • Keep Filter - when using search, tick the checkbox to make the column filters available

  • Saved Searches - press Saved Searches> Save Current Search to save your current search parameters and filtered columns, or Saved Searches > Manage Searches to edit or delete existing searches

πŸ“— TIP

To learn more about saved searches, read our article Working with Saved Searches.

  • Reset All Filters - appears when a filter was used; press to reset filters to their default states

  • Bulk Actions - select one or multiple bookings and press to apply an action on your selection; options include

Bulk Action

Description

Delete All

delete all selected requests

  • Show Columns - press to add new columns, or remove existing ones from your current view
    ​

Did this answer your question?