Naming Conventions

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

Type

Naming Convention

Example

Endpoints

Single word objects are all lowercase. Multi-word objects use lowerCamelCase, in which the first letter of the first word is lower case.

telco
purchases

Objects

Single word objects are all lowercase. Multi-word objects use lowerCamelCase, in which the first letter of the first word is lower case.

invoice
lineItems

Attributes/Fields

Single word objects are all lowercase. Multi-word objects use lowerCamelCase, in which the first letter of the first word is lower case.

city
postalCode