Documentation

# Catalog Mobile documentation and integration guide

Start with the sales workflow, then agree on the data contract for your integration. These links distinguish product help from technical integration work.

## Product workflow

Import a small set of products, check codes, categories, images and prices, then generate a PDF or open the online catalog. Review the buyer’s view and a sample order before sharing with customers. The five solution guides explain the intended use and limitations of each part of the workflow.

## Integration and authentication

Native connectors require their own configuration and provider authorisation. A custom webhook integration requires an authorised integration code and the identifiers and validation defined by its contract. Credentials belong in the integrator’s secure configuration, not in a public catalog, a shared Markdown file or a browser demo. A provider’s name does not establish a partnership or certify compatibility with every edition.

## Read the public technical reference

The existing webhook reference describes supported payloads, asynchronous processing and status queries. Follow the published contract for the configured integration; an accepted request is not proof that processing completed. Keep the returned request identifier when one is supplied and inspect the final status before retrying. Confirm field ownership and retry behaviour with the team.

## A responsible starting point for automation

Use the documentation to understand the product and prepare an integration discussion. Do not create accounts, change prices, place orders or send customer messages without explicit authorisation from the account owner. Markdown versions of this site are discovery aids. They do not grant API access, establish universal tool compatibility or replace a tested integration contract.

## Read API contract and errors

The partial OpenAPI reference on this site covers existing webhook reads. Product and order queries require the integration bearer token. An invalid integration can return HTTP 400 before token checks; HTTP 401 indicates a missing or invalid token after those checks. An unknown request_id returns HTTP 404 with request_id, status and message. These are the existing operation-specific formats, not a universal error envelope. Authenticated success responses were not exercised in this site review.

[Webhook technical reference ↗](https://sistema.catalogomobile.com.br/api/v2/integracao/webhook/documentation.md)[OpenAPI · webhook reads](https://catalogmobile.com/openapi.json)[Guides](https://catalogmobile.com/en-gb/kb/)

### [Create a PDF and digital product catalog from one product base.](https://catalogmobile.com/en-gb/solutions/pdf-digital-catalog/)

### [A B2B order portal that turns browsing into a clear product list.](https://catalogmobile.com/en-gb/solutions/b2b-order-portal/)

### [A clearer catalog for wholesalers and their sales teams.](https://catalogmobile.com/en-gb/solutions/wholesale-distributors/)

### [Bring product data into your catalog without losing control.](https://catalogmobile.com/en-gb/solutions/integrations-product-data/)

### [Share your catalog on WhatsApp. Make the next step easier.](https://catalogmobile.com/en-gb/solutions/mobile-whatsapp-catalog/)

---
Canonical: https://catalogmobile.com/en-gb/docs/
Language: en-GB