Sage Sales Management API Docs
v4 OpenAPI
API Reference · v4

Sage Sales Management API

This new version of our Application Programming Interface (API) represents a huge step forward. It is more powerful and easier to use than the previous version. Here you will find all the guidance you need to build integrations for the Sage Sales Management application.

Getting Started

Base URL
https://api.forcemanager.com/api/v4
Authentication

POST /api/v4/login → token in X-Session-Key

Format

All requests and responses use JSON. Set Content-Type: application/json.

Transport

All requests must be made over HTTPS.

Endpoints

The API is designed around the concept of resources. A resource is related to an entity within Sage Sales Management — Accounts, Opportunities, Products, Contacts, and so on. Endpoints perform a specific function and return data in JSON format.

Requests

All data is sent and received in JSON format. All API requests require authentication. Four HTTP verbs are supported:

  • GET — retrieves data
  • POST — adds new records
  • PUT — partial update of records
  • DELETE — deletes records

Filters, Orders and Language

Apply filters using SQL-style query string parameters with operators: =, >, LIKE, AND, OR. Use the order param to sort results and lang for response language (en, es, pt, it, fr, de, ru).

API Errors

Code Name Description
900 Connection Error The database connection cannot be established
901 Internal data Error The SQL is not generated correctly
910 Resource not exist The resource you provide doesn't exist

Security

All requests to the API must be made over HTTPS. Using HTTPS ensures that all information exchanged is encrypted and cannot be intercepted.

Data Transfer

All entities sent and received are encoded as JSON objects. The API is compliant with the W3C CORS specification, allowing requests from any properly-authorized origin domain.

Release Notes

01/08/2021

Changes in Contacts — the property gender is now returned in value list format instead of binary.

18/06/2020

Fixed: POST on Users was ignoring the isActive field.

08/05/2020

Changes in tblFamiliasProd — property name renamed to description.

Resources