AMA Sage API

Sign in

AMA Sage API

Choose a new password

Your password is temporary. Choose a new one (at least 12 characters) to continue.

AMA Sage API

Dashboard

The Sage SDK licence (serial number / auth key) is not configured — reads work, but creating and updating customers will return 503.

API calls — last 14 days

Server

Top API users (7 days)

Sage databases (7 days)

Recent errors

Audit log

API users

Systems that call the API with Basic authentication. Each can only use the Sage databases ticked for it.

Admin users

People who can sign in to this console. New admins must change their password at first sign-in.

Sage connection

The SQL Server and login the API uses for Sage Evolution. It decides which company databases API users can be given. Changes are tested first and take effect immediately.

Connection

Authentication

In use

Test result

The SQL password is stored encrypted (Windows DPAPI) in AMA_API and is never shown again. The SDK licence stays in secrets.config. Which companies may be used is set under Sage databases.

Sage databases

Which Sage company databases the API may use at all. API users can only be given enabled databases, and calls naming any other database are refused (403). Changes apply immediately.

The API may use

API database

The SQL database holding this API's own data: API users, admin users, the audit log and the settings made in this console (normally AMA_API). It does not have to be on the Sage server. Changes are tested first and take effect immediately.

Connection

Authentication

In use

Test result

The target database must already have the AMA_API tables (run database\AMA_API.sql on that server first). Users, the audit log and the Sage settings are not copied: the API uses whatever that database contains. If it has no admin users, your admin login is copied into it so you can still sign in. This setting is stored on the web server in App_Data, with the password encrypted.