• You must have a username/password that allows you to access Your Sage Active.
  • If you do not yet have access to Sage Active, you can subscribe to or try Sage Active here: Subscribe to Sage Active.
  • Boost your app’s visibility by showcasing it on the MarketPlace.

Introduction

This image outlines two key areas:

  1. Defining your app in Sage Active: This part details the initial registration and configuration of your application within your Sage Active business subscription (FR, ES, DE or PT).
    Here, you will register your app and choose which specific markets (FR, ES/PT, or DE, or any combination of these) your app will target and operate in, allowing for flexible application deployment across different regional markets.

  2. Use of your app by customers in various Sage Active environments: This section focuses on how your app, tailored to specific markets, is utilized by customers within those chosen environments.
    It shows how customers access your application through the respective Public APIs for FR, ES/PT, or DE, ensuring that your app’s functionalities are available to businesses in these specific regions as per your configuration in the first section.

img

Sage Active environments

  • Sage Active is available in three distinct regional environments: FR, ES/PT, and DE.
  • As a developer, you will have a Sage Active business subscription in one of these legislations: FR, ES, DE or PT.
    From this subscription, you can register your application and configure it for the markets you want to target.
  • Although your application is registered from a single business subscription, you can configure it to operate in one or more markets (FR, ES/PT, and/or DE), each with its own Public API and API keys.
  • ES and PT share the same Public API (ES/PT); FR and DE each have their own.
  • For example, you can target FR only, FR and ES/PT, ES/PT only, or all markets (FR, ES/PT, and DE).
  • To do this, use the Solutions tab of your application to define the settings for each target market (Solution FR, Solution ES/PT, or Solution DE).
  • For each Sage Active environment where your app operates (FR, ES/PT, or DE), you will need a Sage ID account authorized in that environment.
    This account must belong to a user with access to the corresponding Sage Active instance.

    • Here are the different URLs for using the FR, ES / PT, DE API and authenticating your application.
    • The URLs for the SBCAuth authentication service are the same for all three production environments.
    • In Postman environnement baseAddress = API Address without /graphql.

      Sage Active FR
      API Address
      Sage Active ES / PT
      API Address
      Sage Active DE
      API Address
      Authentication
      AuthUrl
      AccessTokenUrl
      Revoke Token URL prod