Skip to main content

API ENUMs

This page details the predefined values (ENUMs) used across the Koncili API.


This documentation describes all enumerated types (ENUMs) used in the Marketplace API, including their possible values, descriptions, and related endpoints.

ENUM Overview​

ENUMs are used to standardize:

  • Order statuses
  • Payment methods
  • Financial release types (lançamentos)
  • Classification of postings in the financial taxonomy
  • Other fields with predefined value sets
How to use

Always reference the exact values as documented below, including case sensitivity and underscores.

Important

When integrating with the API:

  • Consult this documentation for the accepted ENUM values for each endpoint.
  • Validate values before sending them to the API.
  • Implement proper handling for responses containing unknown or unexpected ENUMs.
  • Periodically update your implementation as new ENUM versions are released.

ENUM Descriptions​

Order Status​

ENUM ValueDescriptionRelated Endpoints
INVOICEDOrder has been invoiced
POST /order
GET /order
POST /reconciliation
PAID_WAITING_DELIVERYSent
POST /order
GET /order
POST /reconciliation
CONCLUDEDDelivered
POST /order
GET /order
POST /reconciliation
CANCELEDOrder has been canceled
POST /order
GET /order
POST /reconciliation

Payment Methods​

ENUM ValueDescriptionRelated Endpoints
IN_CASHOne-time full payment (In cash)
POST /order
GET /order

Financial Release Types​

ENUM ValueDescriptionRelated Endpoints
COMISSIONSales commission
POST /order
GET /order
POST /reconciliation
SHIPShipping/Freight
POST /order
GET /order
POST /reconciliation
RETURN_COMISSIONCommission refund/reversal
POST /order
GET /order
POST /reconciliation
RETURN_SHIPShipping refund/reversal
POST /order
GET /order
POST /reconciliation
SALEDirect sale
POST /order
GET /order
POST /reconciliation
ADJUSTMENTAdjustment
POST /order
GET /order
POST /reconciliation

Financial Taxonomy​

The financial taxonomy classifies every posting into four nested levels, derived from the settlement type (extractType) of the posting itself. The four fields are always returned, and always filled in, by:

JSON fieldLevelWhat it representsENUM valueReturned label (en)
functionGrouperL0 — Function GrouperBroadest nature of the posting: revenue, expense, other or legacyREVENUE_ROOTRevenue
financialFunctionL1 — Financial FunctionRole of the posting within the grouper, for example revenue vs. revenue reductionREVENUERevenue
financialGroupingL2 — Financial GroupingAnchor level: uniquely identifies the classification and determines the other threeREVENUE_SALERevenue - Sale
categoryL3 — CategoryAccounting nature of the posting: sale, commission, shipping, tax and the likeSALESale
Values translated according to the language

Just like the description field of the settlement type, the four taxonomy fields are translated: the API returns the label in the language of the request, not the ENUM value. The tables on this page list the ENUM because it is the canonical enumeration of the taxonomy — what travels in the JSON is the matching label, shown in the "Returned label (en)" column.

When no translation is registered for a value, the API returns the translation key itself: taxonomy.<VALUE> for L0, L1 and L2, and taxonomyCategory.<VALUE> for L3 — for example, taxonomy.FOO. Treat that shape as an unknown value.

How to use

The four taxonomy fields are meant for display and human reading: because they are translated, they must not be used as an integration key. For the automatic accounting mapping in your ERP, use the invariant technical codes — extractType on the items of unresolveds/concilieds, and code on releasetype.

It still holds that L2 is the anchor level: once you know the financial grouping, the other three levels are determined. The remaining fields spare you from the combination table when totalling at higher levels.

L0 — Function Grouper (functionGrouper)​

ENUM valueDescriptionReturned label (en)
REVENUE_ROOTPostings related to the seller revenueRevenue
EXPENSE_ROOTPostings related to expenses charged by the marketplaceExpense
OTHER_ROOTMovements that are neither revenue nor expense (transfers, blocks, informational entries)Others
LEGACY_ROOTTypes not yet reclassified into the current taxonomyLegacy

L1 — Financial Function (financialFunction)​

ENUM valueGrouper (L0)DescriptionReturned label (en)
REVENUEREVENUE_ROOTRevenue — amount in favor of the sellerRevenue
REVENUE_REDUCTIONREVENUE_ROOTRevenue reduction — refund or return that reduces revenueRevenue Reduction
EXPENSE_OPERATIONALEXPENSE_ROOTOperating expense charged to the sellerOperational Expenses
EXPENSE_COMPENSATIONEXPENSE_ROOTExpense compensation — refund of an expense charged previouslyExpense Compensation
OTHER_INCOMINGOTHER_ROOTIncoming amount that is not revenueOthers - Incoming
OTHER_OUTGOINGOTHER_ROOTOutgoing amount that is not an expenseOthers - Outgoing
OTHER_NEUTRALOTHER_ROOTNeutral posting — neither incoming nor outgoingOthers
LEGACYLEGACY_ROOTLegacy classification, kept for types not yet reclassifiedLegacy

L3 — Category (category)​

ENUM valueDescriptionReturned label (en)
SALEProduct saleSale
COMMISSIONCommission charged by the marketplaceCommission
SHIPPINGShipping and logisticsShipping and Logistics
CAMPAIGNCampaigns, coupons and promotional actionsCampaign
TAXTaxes and dutiesTaxes
WITHHOLDING_AND_RELEASEWithholding and release of amountsWithholdings and Releases
PURCHASEPurchase of products or services from the marketplacePurchases
ANTICIPATIONReceivables anticipationAnticipations
LEGALAmounts of legal originLegal
PENALTYFines and penaltiesPenalties
NOTICEInformational postingInformational
SUBSCRIPTIONSubscriptions and recurring feesSubscription
TRANSACTIONTransfers and financial movementsTransactions
OTHERRemaining postingsOthers
LEGACYLegacy categoryLegacy

Valid combinations​

Each Financial Grouping (L2) belongs to exactly one Financial Function, one Function Grouper and one Category. The table below lists every combination that exists today.

financialGrouping (L2)financialFunction (L1)functionGrouper (L0)category (L3)L2 label (en)
REVENUE_SALEREVENUEREVENUE_ROOTSALERevenue - Sale
REVENUE_SHIPPINGREVENUEREVENUE_ROOTSHIPPINGRevenue - Shipping
REVENUE_CAMPAIGNREVENUEREVENUE_ROOTCAMPAIGNRevenue - Campaign
REVENUE_TAXREVENUEREVENUE_ROOTTAXRevenue - Taxes
REVENUE_TRANSACTIONREVENUEREVENUE_ROOTTRANSACTIONRevenue - Transactions
REVENUE_OTHERREVENUEREVENUE_ROOTOTHERRevenue - Others
REVENUE_REDUCTION_SALEREVENUE_REDUCTIONREVENUE_ROOTSALERevenue Reduction - Sale
REVENUE_REDUCTION_SHIPPINGREVENUE_REDUCTIONREVENUE_ROOTSHIPPINGRevenue Reduction - Shipping
REVENUE_REDUCTION_CAMPAIGNREVENUE_REDUCTIONREVENUE_ROOTCAMPAIGNRevenue Reduction - Campaign
REVENUE_REDUCTION_TRANSACTIONREVENUE_REDUCTIONREVENUE_ROOTTRANSACTIONRevenue Reduction - Transactions
REVENUE_REDUCTION_TAXREVENUE_REDUCTIONREVENUE_ROOTTAXRevenue Reduction - Taxes
REVENUE_REDUCTION_OTHERREVENUE_REDUCTIONREVENUE_ROOTOTHERRevenue Reduction - Others
EXPENSE_OPERATIONAL_COMMISSIONEXPENSE_OPERATIONALEXPENSE_ROOTCOMMISSIONExpenses - Commission
EXPENSE_OPERATIONAL_SHIPPINGEXPENSE_OPERATIONALEXPENSE_ROOTSHIPPINGExpenses - Shipping and Logistics
EXPENSE_OPERATIONAL_CAMPAIGNEXPENSE_OPERATIONALEXPENSE_ROOTCAMPAIGNExpenses - Advertising and Campaigns
EXPENSE_OPERATIONAL_TAXEXPENSE_OPERATIONALEXPENSE_ROOTTAXExpenses - Taxes
EXPENSE_OPERATIONAL_PENALTYEXPENSE_OPERATIONALEXPENSE_ROOTPENALTYExpenses - Penalties
EXPENSE_OPERATIONAL_PURCHASEEXPENSE_OPERATIONALEXPENSE_ROOTPURCHASEExpenses - Purchases
EXPENSE_OPERATIONAL_ANTICIPATIONEXPENSE_OPERATIONALEXPENSE_ROOTANTICIPATIONExpenses - Anticipations
EXPENSE_OPERATIONAL_LEGALEXPENSE_OPERATIONALEXPENSE_ROOTLEGALExpenses - Legal
EXPENSE_OPERATIONAL_SUBSCRIPTIONEXPENSE_OPERATIONALEXPENSE_ROOTSUBSCRIPTIONExpenses - Subscription
EXPENSE_OPERATIONAL_OTHEREXPENSE_OPERATIONALEXPENSE_ROOTOTHERExpenses - Others
EXPENSE_COMPENSATION_COMMISSIONEXPENSE_COMPENSATIONEXPENSE_ROOTCOMMISSIONCompensation - Commission
EXPENSE_COMPENSATION_SHIPPINGEXPENSE_COMPENSATIONEXPENSE_ROOTSHIPPINGCompensation - Shipping and Logistics
EXPENSE_COMPENSATION_CAMPAIGNEXPENSE_COMPENSATIONEXPENSE_ROOTCAMPAIGNCompensation - Advertising and Campaigns
EXPENSE_COMPENSATION_TAXEXPENSE_COMPENSATIONEXPENSE_ROOTTAXCompensation - Taxes
EXPENSE_COMPENSATION_PENALTYEXPENSE_COMPENSATIONEXPENSE_ROOTPENALTYCompensation - Penalties
EXPENSE_COMPENSATION_PURCHASEEXPENSE_COMPENSATIONEXPENSE_ROOTPURCHASECompensation - Purchases
EXPENSE_COMPENSATION_ANTICIPATIONEXPENSE_COMPENSATIONEXPENSE_ROOTANTICIPATIONCompensation - Anticipations
EXPENSE_COMPENSATION_LEGALEXPENSE_COMPENSATIONEXPENSE_ROOTLEGALCompensation - Legal
EXPENSE_COMPENSATION_SUBSCRIPTIONEXPENSE_COMPENSATIONEXPENSE_ROOTSUBSCRIPTIONCompensation - Subscription
EXPENSE_COMPENSATION_OTHEREXPENSE_COMPENSATIONEXPENSE_ROOTOTHERCompensation - Others
OTHER_INCOMING_TRANSFEROTHER_INCOMINGOTHER_ROOTTRANSACTIONTransfers - Incoming
OTHER_INCOMING_INFORMATIONOTHER_INCOMINGOTHER_ROOTNOTICEInformational - Incoming
OTHER_INCOMING_UNBLOCKINGOTHER_INCOMINGOTHER_ROOTWITHHOLDING_AND_RELEASEReleases - Unblocking
OTHER_INCOMING_OTHEROTHER_INCOMINGOTHER_ROOTOTHEROther Incoming
OTHER_OUTGOING_TRANSFEROTHER_OUTGOINGOTHER_ROOTTRANSACTIONTransfers - Outgoing
OTHER_OUTGOING_INFORMATIONOTHER_OUTGOINGOTHER_ROOTNOTICEInformational - Outgoing
OTHER_OUTGOING_BLOCKINGOTHER_OUTGOINGOTHER_ROOTWITHHOLDING_AND_RELEASEWithholdings - Blocking
OTHER_OUTGOING_OTHEROTHER_OUTGOINGOTHER_ROOTOTHEROther Outgoing
OTHER_NEUTRAL_OTHEROTHER_NEUTRALOTHER_ROOTOTHEROthers
LEGACY_V1LEGACYLEGACY_ROOTLEGACYOthers - Legacy
New values

New groupings may be created as new settlement types are mapped. Handle unknown values gracefully, as recommended at the top of this page.

Notification Types​

ENUM ValueDescriptionRelated Endpoints
TEST_NOTIFICATIONRegistered URL test
POST to the integrator's URL
ACCOUNT_CREATEDAccount created
POST to the integrator's URL
RECONCILIATION_COMPLETEDReconciliation completed
POST to the integrator's URL
BLOCKED_TEMPORARYTemporary block
POST to the integrator's URL
BLOCKED_PERMANENTPermanent block
POST to the integrator's URL
UNLOCKEDAccount unlocked
POST to the integrator's URL