Overview

All communication between third party applications and Fibery's services is done via standard hypertext protocols, whether they be HTTP or HTTPS. All third party applications are expected to adhere to a particular API format as outlined in this documentation. The underlying technologies used to develop these third party applications are up to the individual developer.

All communication with third party services is done via Fibery reporting applications gallery. Users may register their applications with Fibery by providing a HTTP or HTTPS URI for their service. The service must be accessible from the internet in order for the applications gallery to successfully communicate with the service. It is highly recommended that service providers consider utilizing HTTPS for all endpoints and limit access to these services only to IP addresses known to be from Fibery custom app.

In essence, applications gallery service acts as a proxy between other Fibery services and the third party provider with some added logic for account and filter storage and validation.

Tutorials

• Simple app
• App with schema

API

• Overview
• Domain
• Fields types
• GET /
• POST /
• POST /validate
• POST /datalist
• GET /logo
• POST /oauth1/v1/authorize
• POST /oauth1/v1/access_token
• POST /oauth2/v1/authorize
• POST /oauth2/v1/access_token
• POST /schema
• POST /validate/filter
• POST /count

Specifications

• Date range grammar

Examples

• Overview