Skip to main content

Introduction to Fabrick Platform

Learn how to use Consumer Portal to configure your Fabrick account to enable instant access to our APIs. Or deep-dive into the API features to learn how to start building your integration.

Consumer Portal​

The Fabrick Customer Portal is a web portal that enables Fabrick customers to configure their account.

Here you can find the tutorial.

The Customer Portal can be accessed directly from the Login menu item on top of each Fabrick website page. By logging in to the private profile, you are enabled to access the following functionalities:

  • Personal information. You can review the personal information related to your account.
  • Account configuration. A section that allows the configuration of account-level settings (e.g., payment calls thresholds).
  • APIKey-level configurations. A section that allows the configuration of the following security options for each of your APIKeys: IP address whitelist, APIKey-level payment calls limitations, and redirect URLs.

We support the access to your private profile by means of Fabrick Credentials or Sella Credentials. If you are not sure about the credentials to use for the access to your private profile, please contact our Customer Support.

Access with Fabrick Account​

In order to log in into your private profile, you will need your Fabrick customer identification credentials, namely:

  • Your EMAIL.
  • Your PASSWORD.

If you are in trouble with your Fabrick Account access credentials, contact our Customer Support.

API | Overview​

Once you have properly configured your Fabrick Account by accessing your private profile on the Consumer Portal, you are enabled to invoke our APIs.

Fabrick Platform exposes many packages of RESTful web APIs; the platform helps in uniforming and standardizing the services, thus helping final developers to use all the exposed APIs as a coherent and uniform set of functions. 

We have adopted a shared model of API Lifecycle and Environments as common basic concepts to every API package that is exposed.

API Lifecycle​

  • Forthcoming. This stage identifies those API groups which have been accepted for publication, but are still under analysis, so no documentation can be published.
  • Beta Version. This API stage identifies those API groups that have been released - i.e., endpoints are available in MOCKUP | SANDBOX | LIVE environments - but we are still fixing the last screws. These API groups should be used only for experimentation and/or testing purposes; we discourage the use of BETA Version APIs for production purposes.
  • Production. This stage identifies those API groups that are live in production. Only these API groups should be used for production purposes.
  • Deprecated. This stage identifies those API groups that have been replaced by a newer version. You can still use these APIs for production purposes, but you should migrate as soon as possible to the latest available version, since support to these APIs is discontinued.

Environments​

We provide two different environments to access our APIs, each one with different security profiles and limitations.

  • SANDBOX Development and test environment, with full security policy enforcement, API key is required. API invocation returns well-formed dynamic-contents answers, with out-of-sync data.
  • LIVE Production environment, with full security policy enforcement, API key is required. API invocation returns well-formed and online dynamic-contents answers.

Invoking Fabrick Platform APIs​

Once you have defined the environment in which you want to operate, you are ready to invoke your first Fabrick Platform API.

Each API request must be sent through the HTTP protocol, using the correct HTTP verb as documented in the technical endpoint documentation. Each request must have at least the following headers (additional headers may be specified in the technical documentation of each endpoint):

Content-Type : 'application/json'  
Auth-Schema : 'S2S'
Api-Key : '{APIKey}'

The request and response body encoding is always UTF-8.
Required input parameters must be provided as JSON data blocks in each request's body, for example:

{
    "accountNumber" : "{an-account-number}"
}

When more parameters are required, simply provide multiple key/values couples inside the same JSON data block.