### Pendo API Call Headers Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/Page - Feature - Guide IDs/readme.md Demonstrates the required headers for making API calls to Pendo, including content type and integration key. ```http POST https://app.pendo.io/api/v1/aggregation Content-Type: application/json X-Pendo-Integration-Key: $insert-pendo-key$ ``` -------------------------------- ### Aggregate Pendo NPS Responses Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/NPS Data/readme.md This snippet shows how to combine quantitative and qualitative NPS responses from Pendo. It uses the previously obtained poll IDs and the guide ID. The request utilizes 'spawn' to run multiple pipelines and 'join' to aggregate results based on visitorId. ```JSON { "request": "combinedNpsResponses.json", "params": { "yourGuideId": "YOUR_GUIDE_ID", "pollId1": "QUANTITATIVE_POLL_ID", "pollId2": "QUALITATIVE_POLL_ID" } } ``` -------------------------------- ### Get Pendo Poll IDs Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/NPS Data/readme.md This snippet demonstrates how to retrieve poll IDs for Pendo guides. It requires the guide ID, which can be found in the Pendo URL. The output provides the necessary poll IDs for subsequent requests. ```JSON { "request": "getPollIds.json", "params": { "yourGuideId": "YOUR_GUIDE_ID" } } ``` -------------------------------- ### Pendo Events API Request Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/Events/Readme.md This snippet demonstrates a POST request to the Pendo Events API for retrieving event data. It includes the endpoint, required headers, and an example JSON request body. The `daysAgo` parameter controls the data retrieval period, with a recommendation to keep it at 1 for daily processing. ```http POST https://app.pendo.io/api/v1/aggregation Content-Type: application/json X-Pendo-Integration-Key: $insert-pendo-key$ ``` ```json { "query": { "filters": [ { "operator": "daysAgo", "value": 1 } ] } } ``` -------------------------------- ### Retrieve New Users Last X Days API Call Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/User Data/readme.md This API call fetches visitor IDs and first visit timestamps for new users within a specified date range. The default is the last 7 days, but this can be adjusted by modifying the 'filter' value in the request body. It also includes an option to hash visitor IDs for PII protection. ```json { "query": { "visitors": { "new": { "days": 7 } } }, "fields": { "visitors": [ "visitorId", "firstVisit" ] }, "options": { "visitorId": { "hash": true } } } ``` -------------------------------- ### API Request Headers (HTTP) Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/Feature Events Data/readme.md This snippet details the necessary HTTP headers for making a request to the Pendo API. It includes the Content-Type and the Pendo Integration Key. ```http Content-Type: application/json X-Pendo-Integration-Key: $insert-pendo-key$ ``` -------------------------------- ### Pendo API Call Data Structure Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/Feature Events Data/Sample Feature Event Data.txt This JSON structure represents a single record of an API call made to Pendo. It includes details such as account ID, application ID, timestamp, feature ID, event counts, session duration, IP address, server information, and user agent. ```json { "accountId": "tempAccount", "appId": -323232, "day": 1540008000000, "featureId": "uQZVeRyEAODXLqvQJYvN51Ffsek", "numEvents": 5, "numMinutes": 1, "remoteIp": "2405:204:1387:bbac:652a:c0eb:76b8:9177", "server": "www.pendosandbox.com", "userAgent": "Mozilla/5.0 (Mobile; LYF/F90M/LYF_F90M_000-03-06-290818; Android; rv:48.0) Gecko/48.0 Firefox/48.0 KAIOS/2.5", "visitorId": "temp" } ``` -------------------------------- ### Pendo API Request Headers Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/README.md Standard headers required for authentication and content type when making requests to the Pendo v1 Aggregations API. Requires an integration key for secure access. ```JSON Content-Type: application/json X-Pendo-Integration-Key: ``` -------------------------------- ### Page Events Data Request Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/Page Events Data/readme.md This snippet shows the structure of the JSON request body and the necessary HTTP headers to retrieve page event data from the Pendo API. It includes placeholders for the Pendo integration key. ```json { "query": { "pageEvents": { "filters": { "date": "1" } } } } ``` ```http POST https://app.pendo.io/api/v1/aggregation Content-Type: application/json X-Pendo-Integration-Key: $insert-pendo-key$ ``` -------------------------------- ### Retrieve Feature Events Data (JSON) Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/Feature Events Data/readme.md This snippet shows the JSON request body structure for fetching feature event data from the Pendo API. It includes parameters for specifying the data retrieval period. ```json { "report": "featureEvents", "params": { "days": 1 } } ``` -------------------------------- ### Retrieve Anonymous Visitors API Call Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/User Data/readme.md This API call retrieves all designated Anonymous Visitors from your Pendo subscription. It requires a POST request to the Pendo aggregation endpoint with specific headers. ```json { "query": { "visitors": { "anonymous": true } } } ``` -------------------------------- ### Visitor ID Hashing in Pendo API Source: https://github.com/pendo-io/pendo-etl-api-calls/blob/master/NPS Data/readme.md This snippet illustrates how to hash the visitorId in Pendo API requests for data privacy. The hashing can be removed if not required. This is typically part of a larger request body. ```JSON { "eval": { "visitorId": "hash(visitorId)" } } ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.