Using LiveTail to Diagnose API Requests

Using Live Tail to Diagnose API Requests


Overview


Live Tail is a real-time request monitoring tool built into the Repliers portal. It lets you capture the exact structure of outgoing API requests — including headers, query parameters, and request bodies — so you can verify that your application is sending requests correctly.


This is especially useful when a response isn't behaving as expected and you need to confirm the request your application is actually sending, versus what you intended.


Prerequisites


  • An active Repliers account
  • At least one API key issued under your account
  • An application or tool making requests against the Repliers API



Accessing Live Tail


  1. Navigate to login.repliers.com and sign in to your account.
  2. In the left-hand navigation menu, click Usage.
  3. Select the Live Tail tab at the top of the page.


You are now in the Live Tail view. Incoming requests will appear here in real time as your application makes them.



Selecting an API Key to Monitor


If your account has multiple API keys, you can filter the Live Tail feed to a specific key:


  1. Look for the API Key selector at the top of the Live Tail tab.
  2. Choose the key associated with the integration you want to monitor.
  3. The feed will update to show only requests made with that key.


This is useful when you have separate keys for different environments (e.g., development vs. production) or different client applications.



Reading a Live Tail Entry


Each entry captured in the feed displays the following:


Field

Description

Timestamp

When the request was received by the API

Endpoint

The API path that was called (e.g., /listings)

Method

HTTP method used (GET, POST, PATCH, etc.)

Query Parameters

Any filters or parameters passed in the URL

Request Body

The payload sent with POST or PATCH requests

Response Code

The HTTP status returned (e.g., 200, 400, 422)



Common Use Cases


Verifying filter parameters are being sent correctly
Run a search in your application, then check the Live Tail entry to confirm that all expected query parameters (e.g., city, minPrice, maxPrice) are present and formatted correctly.


Debugging unexpected responses
If you receive a 400 or 422 error, the Live Tail entry will show exactly what was sent, making it easy to spot malformed values, missing required fields, or incorrect data types.


Sharing request details with support
Rather than reconstructing a request from memory, you can copy the exact payload or parameter string from Live Tail and share it with the Repliers support team for faster diagnosis.



Sharing a Request with Support


When contacting support about an unexpected API response, please include:


  1. The timestamp of the request from Live Tail
  2. The full endpoint and query parameters
  3. The request body (for POST/PATCH requests)
  4. The response code received


This allows the support team to reproduce and investigate the issue without any guesswork.



Tips


  • Trigger requests one at a time when debugging, so individual entries are easy to identify in the feed.
  • Use a dedicated test API key if you want to isolate test traffic from live production requests.
  • The feed is real-time — you don't need to refresh the page; new entries will appear automatically as requests come in.

Updated on: 05/08/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!