Skip to main content

Admin > API Post History

The API Post History screen allows admins to monitor and troubleshoot data submissions made to Logixx through integrated API profiles. This feature provides detailed visibility into each post, including payload data, headers, and system responses.

Location

To access this feature, navigate to:
Admin > Service > API Post History


🔍 Filter Options

The top section of the screen includes filters to help you search for specific API posts:

  • Time: Select a date and time range for submitted posts.

  • Status: Filter by result status

  • API Profile Name: Narrow results to a specific API integration or profile.

Filter Controls:

  • Apply – Run the search using selected filters.

  • Clear – Reset all filters.

  • Close – Collapse the filter panel.


📋 Table Columns

The API posts are listed in a table with the following columns:

Column

Description

Posted At

Timestamp when the API post was received.

API Profile Name

Name of the configured API profile.

IP

IP address from which the post originated.

Key

Unique API key or code associated with the post.

Data Source

The system or campaign that originated the data.

Data

Core content/body of the post (truncated view in the table).

Headers

Request headers sent with the API call.

Status

Processing outcome of the API post.

Result

Summary of the result or action taken


🔽 Row Expansion – Detailed View

Each row in the API Post History table includes a downward arrow icon. Clicking it reveals an expanded detailed view of the API post, including:

Overview

Field

Example

Time

5/12/25 03:05:05 PM

IP

50.31.165.18

Path

/api/cgi/post/eb1e029e-209d-4df9-4323-08dbf8695c6e

API Key/Code

eb1e029e-209d-4df9-4323-08dbf8695c6e

Campaign

Alleviate Financial

Status

ConvertSuccess

Result

Updated #475818 Brenda Hockmuth

Headers

The HTTP headers received with the API post are displayed in full JSON format.

Data (Body)

The full request body sent via the API is displayed here. This section often includes form fields, applicant data, or processing notes.

Did this answer your question?