Pendo Feedback API

## Who is this for? This documentation is for developers creating their own integration with [Feedback's](https://www.pendo.io/product/feedback/) API. If you are doing a standard integration, there's a really easy [Javascript integration](https://help.receptive.io/hc/en-us/articles/209221969-How-to-integrate-Receptive-with-your-app) that you should know about before you go to the effort of building your own integration. ## Authentication API calls generally need to be authenticated. Generate an API Key at https://feedback.pendo.io/app/#/vendor/settings?section=integrate. This key should then be added to every request as a request header named 'auth-token' (preferred), or as a query parameter named 'auth-token'. ## Endpoint API endpoint is https://api.feedback.eu.pendo.io / https://api.feedback.us.pendo.io depending where your datacenter is located. ## Notes API endpoints are being added to this documentation as needed by customers. If you don't see an endpoint you need please contact support and if it exists we'll publish the docs here. The 'try it out' feature on this documentation page will probably be blocked by your browser because the Access-Control-Allow-Origin header has its value set by the Feedback server depending on your hostname. ## Generating client code This documentation is automatically generated from an OpenAPI spec available [here](http://apidoc.receptive.io/receptive.swagger.json). You can use Swagger to auto-generate API client code in many languages using the [Swagger Editor](http://editor.swagger.io/#/)

Description supplied by the publisher; it is a claim, not verified evidence.

Name
apisguru:pendo.io
Listed in
APIs.guru
Publisher
pendo.io
Latest version
1.0.0
Published
2021-06-30
Evidence
Listed only, not analyzed yet

What a full analysis of Pendo Feedback API checks

Not checked yet. About 60 tools are analyzed every hour; each check links to its source when it runs:

Before you install it

  1. Open the repository and confirm the account is the one you expect: look-alike names are common.
  2. Read what it asks for: files, accounts, network access and credentials it needs.
  3. Prefer a version from a verified publisher when one exists.

Search the catalog · How UND Assay checks tools