Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Provide your API keys to generate a Bearer Token that needs to be used as part of every future request.

Obtaining your Flexiti API Keys

  • Go to our Developer Portal

  • Create a Developer Portal Account to receive API keys and set up your trust URL (or IP).

    • Be sure to keep them secure!

  • Review the API documentation

  • Use your credentials using Postman or Swagger

  • Implement the TRAINING (test) version on your Staging environment and test thoroughly

  • Implement the PROD (live) version on your Production environment and review

Environments

All API requests exist in MERCHANT INTEGRATION, TRAINING and PRODUCTION environments. All objects - customers, plans, transactions, and so forth created in one environment do not exist in the other.

In our MERCHANT INTEGRATION environment:

  • Transactions and customer accounts generated in this environment are only treated as test objects.

  • This environment is considered an “integration” environment

  • We introduce new code to this environment prior to production Releases to allow Merchants an opportunity to integrate the new code with their current implementations

  • Here is our API Changelog & Release Schedule

  • References: https://posapi-training.flexiti.fi/flexiti/pos-api/

In our TRAINING environment:

  • Transactions and customer accounts generated in this environment are only treated as test objects.

  • Our training environment is scrubbed from time to time

  • This environment is considered a “test” environment

  • References: https://posapi-training.flexiti.fi/flexiti/pos-api/

In our PRODUCTION environment:

  • Customer accounts generated in this environment hit the Credit Bureau

  • Transactional data generated in this environment are stored in Flexiti’s production systems

  • This environment is considered a “Live” production environment

  • References: https://posapi.flexiti.fi/flexiti/pos-api/

Errors

Flexiti uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, a transaction failed, etc.). Codes in the 5xx range indicates an error with Flexiti's servers.

...

When we make backwards-incompatible changes to the API, we release new versions. The current version is version 2.5. A Change log can be found here -: https://flexiti.atlassian.net/wiki/x/GQCRAg

...

  • Adding new API endpoints

  • Adding new parameters to existing endpoints

  • Adding new data elements to existing response schema

  • Adding new error types and error response codes

  • Changing the length or content of any API parameter

...

Read More:

Child pages (Children Display)