Yes. Krokul CRM integrates with OLX through the Partner API for seller business accounts. A buyer message under your advert becomes a conversation in Krokul Communications, a contact and a deal, and the manager replies from Krokul into the same OLX thread. OLX adverts are published and updated from Krokul catalog products and are taken down when the product is sold.
Krokul reads /threads and takes the threads with unread messages. A new thread with a buyer becomes a conversation in Communications, and the interlocutor from interlocutor_id becomes a contact with the name from /users/{id}. The deal gets the advert title from advert_id and the OLX source, so the seller sees which adverts bring buyers.
The manager answers the buyer in the Krokul conversation window, and the text goes to OLX through POST /threads/{threadId}/messages. Once the message is read, Krokul sends the mark-as-read command, so the unread counter in the OLX account matches Krokul. The whole correspondence stays on the contact card next to calls and emails.
The name, description, price and photos live in the Krokul catalog. For a new product, Krokul creates an advert through POST /adverts with the category attributes from /categories/{categoryId}/attributes, and passes a price change to PUT /adverts/{advertId}. Krokul keeps the advert ID as an external key of the product.
When a deal is won and the product stock reaches zero, Krokul sends the deactivate command with is_success, and the OLX advert stops taking questions. The product returns to the warehouse, and the activate command opens the advert again.
| OLX | Direction | Krokul | When |
|---|---|---|---|
| Thread (/threads): advert_id, interlocutor_id, unread_count | OLX → Krokul | Conversation in Communications and deal | A new thread or an unread message |
| Thread messages (/threads/{threadId}/messages) | OLX ↔ Krokul | Message in the conversation | The buyer writes or the manager replies |
| User (/users/{id}) | OLX → Krokul | Contact with a name | The first message from a person |
| Thread command mark-as-read | Krokul → OLX | Read conversation | The manager opens the conversation |
| Advert (POST /adverts, PUT /adverts/{advertId}) | Krokul → OLX | Catalog product with an external key | A new product or a price and description change |
| Advert commands activate, deactivate | Krokul → OLX | Product stock, won deal | The product runs out or returns to the warehouse |
| Advert statistics (/adverts/{advertId}/statistics) | OLX → Krokul | Product card | Polling on a schedule |
contact/api-create and card/api-create, store the thread ID through externalRef/api-upsert, and write messages to the feed through activity/api-create.card.won, check the x-crm-signature header and take the advert down with the deactivate command.Yes. Buyer messages from OLX become conversations, contacts and deals in Krokul, the manager replies from Krokul, and adverts are published and taken down from catalog products.
No. OLX opens access only to the adverts of the account that authorized the app.
No. OLX provides no API test environment and suggests testing the integration on a separate OLX account.
On a schedule and within the OLX limit of 4500 requests in five minutes from one IP address. Going over the limit blocks requests for 30 minutes, so Krokul reads only the threads with unread messages.
OLX sends no events about new messages, so Krokul checks threads on a schedule. The Partner API allows at most 4500 requests in five minutes from one IP address, and access covers only the adverts of the account that authorized the app.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
OLX is a trademark of its owner. Krokul is not affiliated with OLX.
