API categories organised by responsibility
Each API surface should reflect the service responsible for the underlying business object and enforce the correct tenant, permission and identity context.
Ready to move forward?
ACCOUNTING
Accounting
Financial projections and reporting
Billing
Invoices, balances and payments
Commerce
Catalogue, customers and orders
Operations
Property, lending and workflow
Current API Categories
Detailed endpoint documentation can be exposed progressively as each product surface is approved for external use.
The scope is shaped around the customer journey, commercial objective and operating environment rather than forcing every client into the same package.
“
The API should point to the service that owns the fact.
This prevents customer-facing applications from becoming accidental duplicate operational systems.
API Evaluation Flow
01
Identify
Define the business object or action the integration needs.
02
Locate
Use the authoritative NewEdge360 service responsible for it.
03
Authorise
Agree the data and actions the integration may access.
04
Integrate
Implement the contract with error and retry handling.
API Catalogue Questions
Endpoint documentation should be published for approved APIs as each product surface is made available.
Yes. FMG can assess the use case and determine whether an existing interface fits.
Yes, when appropriately scoped and protected credentials are not exposed.
NewEdge360 integrations should preserve the relevant tenant and organisational context.