Skip to main content
POST
/
monitors
/
process
/
retry
Retry processing a monitor
curl --request POST \
  --url https://api.pubrio.com/monitors/process/retry \
  --header 'Content-Type: application/json' \
  --header 'pubrio-api-key: <api-key>' \
  --data '
{
  "monitor_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "monitor_log_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "is_use_original_destination": true,
  "profile_id": 123
}
'
{
  "data": {
    "monitor_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "delivery_result": {
      "is_success": true,
      "error_message": null,
      "response_status_code": 200,
      "response_payload": "...",
      "retry_attempt": 0
    },
    "total_credit": 59,
    "processing_time_ms": 7541
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.pubrio.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
pubrio-api-key
string
header
required

A unique API token that represents the actions you perform through the API and the corresponding permissions and operations. You can create it through the Settings section.

Body

application/json
​
monitor_id
string<uuid>
required

Unique identifier of the monitor.

​
monitor_log_id
string<uuid>
required

Unique identifier of the monitor log entry to retry.

​
is_use_original_destination
boolean

When true, uses the destination configuration snapshot from the original log entry instead of the current monitor config.

​
profile_id
integer

Optional. An identifier for the user profile (workspace) making the request. This is no longer required as the API key already includes your workspace information. If provided, it helps in associating the lookup with a specific user, allowing for data retrieval and credit tracking.

Check out user details endpoints under the Profile tab for more information.

Response

Successful response containing the retry execution results.

​
data
object