BETA

You must now create your first app and associate it with Sage Active Public API V0 to obtain a Client ID, a Client Secret and a Subscription Key necessary to access Sage Active data.
After choosing to associate this app with Sage Active Public API V0 you will get its keys.

  1. Click the Apps tab or the Next button.
    A screen prompts you to add your first application, click on the button Add a new application

    img

  2. The screen for defining a new application appears:

    • Identify your application, all this information can be used to publish the description of your application.

      • Name: User-friendly title of the application.
      • Description: Clear explanation for a customer describing the interest of your application.
      • Url: A link to one of your sites providing more detailed information about your application.
      • Contact email: An email address that your customers or Sage can use to contact you about your application.
    • Qualify the type of application desired:

      Attention
      In the context of this quickstart, please choose Web Application to remain consistent with the rest of the journey.

      • Web Application: classic web application that can use a Client Secret.
      • Mobile Application: native application for mobile, for security the Client Secret is not used.
      • Single Page Application: a web application accessible via a single web page, for security the Client Secret is not used

    img

  3. You will now choose the Sage Active solution.

    Note
    This interface is defined to propose to develop applications using several public APIs.
    Currently only the Sage Active API is offered.

    Choose Sage Active Public API V0 by switching the on/off button to on.

    img

  4. The API information form appears.

    img

  5. Qualify the form information:

    Main information:

    • Callback URLs: List of authorized Callback URLs. You must fill at least one URL.
    • Logout URL: List of authorized Callback URLs.
    • Permissions: Permissions required by your application, by default Read and Write.

      Attention
      In the context of this quickstart, please choose Read Sage Active Data and Write Sage Active Data to remain consistent with the rest of the journey.

    You can also define several other URLs according to the needs of your application:

    • Allowed Origins: Authorized URL for call from Javascript to Auth0.
    • Web origins: Url authorized for request using Cross-Origin-authentication.

    Tip
    For each type of URL you can define several URLs to test your application in different environments.
    Click Add button to add a new field.

    img

  6. Once the information is filled in, click on the Save button.
    Your Client ID, Client Secret, Subscription keys are then generated.

    • Client ID, Client Secret will be needed to authenticate your application to Sage Active Public API V0.
    • Subscription keys are used to follow the consumption of Sage Active Public API V0.
    • Click on the eye icon to the right of the Client Secret to reveal it
    • You can renew the Client Secret at any time by clicking on the Renew icon, be careful in this case you will have to update it in your application.

    img

    • If your application type is not Web Application, the Client Secret will not be visible because it cannot be used in this context.
    • There is a primary key and a secondary key for the Subscription Key, for example this allows you to temporarily share a key, then revoke it later by generating a new key.
  7. Click on the Close button. The application you just created now appears in the list of applications.
    You can change its settings at any time.

    img


Congratulations! Your app is now created.

In the next step, before starting to test Sage Active Public API V0 with Postman, you will access to an organization in Sage Active and consult the list of Journals.
You will then be able to verify that you are accessing the same list of Journals during your first call to Sage Active Public API V0.