PheedLoop API

Welcome to PheedLoop's API Documentation! We'd love to hear your feedback on what's available so far and any additions you'd like to see. Don't hesitate to reach out to our team directly or to [[email protected]](https://mailto:[email protected]). In order to authenticate with our API, you require three things: - API Key - API Secret - Organization Code You can find all this information from your Integrations tab in the Dashboard. You can find all this information [here](https://dash.pheedloop.com/settings/integrations/). If that link does not work for you, you can manually navigate to the page by logging into your Dashboard, then going to **Settings -> Integrations -> Rest API**. The **API Key** and **API Secret** are used in the header of every request and should look like this: | Header Key | Value | | --- | --- | | X-API-KEY | | | X-API-SECRET | | The **Organization Code** is used in the URL of requests. For example: `https://api.pheedloop.com/api/v3/organization/ORGANIZATION-CODE/validateauth/` All URLs should end in a `/`. ## Versioning For documentation purposes, we tag each release of our API with a new version number which signifies any changes. These versions can be used to compare the publicly available version of the API to this documentation. We follow a major-minor-patch system: | Type | Description | Example | | --- | --- | --- | | **Major** | Feature and breaking or non-backwards compatible changes | v2.0.0 -> v3.0.0 | | **Minor** | Feature and non-breaking changes that are backwards compatible | v3.0.0 -> v3.1.0 | | **Patch** | Bug fixes | v3.0.0 -> v3.0.1 | We do not offer different active versions of the API, but the current version can be retrieved from all response headers, via the `PheedLoop-API-Version` field. It usually will match the latest release tag documented, but during roll outs the Documentation may be slightly ahead. Use this field to validate which version you are referencing.