PTSV3

Introduction

PTSV3 allows you to create endpoints (we call them "Bins") to collect HTTP requests. You can send any request method to your bin's URL. The request, including its headers, query parameters, and body, will be recorded for inspection via the web UI or the API.

Note: Free and Anonymous accounts can view the contents of POST and GET requests. Other methods like PUT, PATCH, and DELETE are recorded but require a Developer Plan to view.

Sending Requests

To record a request, simply send any HTTP request to your bin's URL. For example, to use a bin named mytest, you would send a request to:

http://ptsv3.com/mytest

Example: Sending a POST request with cURL

This is the most common use case. The body can be JSON, form data, XML, or plain text.

curl -X POST \
  -H "Content-Type: application/json" \
  -d '{"user_id": 123, "event": "login_success"}' \
  http://ptsv3.com/mytest

Example: Sending a GET request with cURL

Unlike a browser, sending a GET request with a tool like cURL will be recorded in your bin's history.

curl -X GET "http://ptsv3.com/mytest?product_id=abc&status=active"

API Endpoints

You can programmatically retrieve the data collected by your bin using the following read-only API endpoints.

Get All Requests

Returns a JSON array of requests. Use the optional since query parameter to fetch only requests that have arrived after a specific request ID (a Unix millisecond timestamp), useful for polling.

• Method: GET
• URL: /api/<bin_name>/updates

# Get all requests for the 'mytest' bin
curl http://ptsv3.com/api/mytest/updates

Get Latest Request

Returns a single JSON object for the most recent request in a bin.

• Method: GET
• URL: /api/<bin_name>/latest

curl http://ptsv3.com/api/mytest/latest

Get a Specific Request

Returns a single JSON object for a request matching the specified request_id.

• Method: GET
• URL: /api/<bin_name>/<request_id>

curl http://ptsv3.com/api/mytest/1678886400123

Data Structure

A successful API call will return a JSON object (or an array of objects) with the following structure. For gated requests on Free/Anonymous plans, most fields will be replaced by a `locked_content` message.

{
  "id": 1678886400123,
  "method": "POST",
  "headers": {
    "Content-Type": "application/json",
    "User-Agent": "curl/7.81.0",
    ...
  },
  "query_params": {
    "source": "test"
  },
  "body": "{\"key\":\"value\"}",
  "ip_address": "127.0.0.1",
  "timestamp": "2025-03-15T12:00:00.123456+00:00",
  "is_pro_feature": false
}

Legacy Support

To assist users migrating from older versions, PTSV3 maintains limited, permanent redirects for some legacy URL formats. This is a best-effort patch job, and we highly recommend updating any tools or scripts to use the new, more robust API endpoints for better performance and reliability.

• /t/<bin_name> now redirects to /<bin_name>
• /t/<bin_name>/post and /t/<bin_name>/post/json now redirect to /api/<bin_name>/latest