Demander integration with Cayena

Cayena calls the Demander API. Demander does not send data to Cayena on its own.

Cayena is a marketplace. The Cayena account and support stay with Cayena. Demander is not a Cayena product.

How the integration works

Each company has one configuration. It holds the token, the order vendor, the catalog price list, and the status and unit mapping.

1. Cayena authenticates with the company code and the token generated in Demander.
2. It reads the catalog of active products on that price list.
3. It looks up or creates the customer by CPF or CNPJ.
4. It sends the order. The same Cayena number does not create a second order.
5. It reads the status and, once the ERP stores the key, the NF-e.

The order is created with origin Cayena, on the vendor and initial status from the configuration. Status changes and the invoice follow the normal Demander flow, usually through the ERP integration.

What each side does

Who	Responsibility
Cayena	Authenticate, read the catalog, send customer and order, read status and NF-e
Demander	Validate the call, store customer and order, return catalog, status and NF-e key
Company ERP	Update the order status and send the invoice through table 170 — Order invoice, with chaveNfe and serieNfe

This API is not the REST Integration API. The address, the token and the format are different.

Before you turn it on

• An active vendor, with a free number range for Cayena orders.
• A price list with the products Cayena may sell. A zero price, or a price only for one customer, does not enter the catalog.
• Every product unit in the mapping. Without the mapping, the catalog listing fails.
• Initial status with orderStatus CONFIRMED, and at least one delivery status.
• An NF-e key with 44 digits on the order invoice, so Cayena can read the invoice.

The screenshots in this documentation are from company 5000 — Empresa de testes time de produto.

Next articles

• Integration setup
• Cayena API