Fonoa API is built using standards and appropriate naming conventions to help out the developers in understanding the entity and attribute in a better way. To help a developer know what type and kind of result they can expect from different attributes, we use the following naming schema.

Type

Naming Convention

Example

Endpoints

The first letter of every word capitalised.

Invoices
Reporting

Objects

All letter are small caps

meta
items
supplier

Attributes / Fields

Each word is in small caps and separated with an underscore (_)

company_name
tin
uid
delivery_date