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:

TypeNaming ConventionExample
EndpointsSingle word objects are all lowercase. Multi-word objects use lowerCamelCase, in which the first letter of the first word is lower case.telco
purchases
ObjectsSingle 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/FieldsSingle word objects are all lowercase. Multi-word objects use lowerCamelCase, in which the first letter of the first word is lower case.city
postalCode