REST API
Connect Indexed PIM to external systems through the app integrations already implemented in the platform. The current codebase focuses on concrete sync endpoints, app-specific API clients, webhook callbacks, and feed delivery rather than a single generic public API surface.
REST API Reference
What “REST API” means in this codebase
The integration layer in Indexed PIM is built around real app modules. WooCommerce, e-conomic, Rackbeat, Business Central, feeds, and webhooks all use HTTP-based APIs, but they are implemented as focused modules with their own clients, controllers, queues, and logs.
That means the platform already handles the practical parts developers need for integration work: connection testing, request building, credential storage, background sync jobs, inbound webhook endpoints, and per-app request logging.
I did not find a single platform-wide public CRUD API module backing this feature page, so this page describes the integration API capabilities that are actually present instead of promising a generic developer API that is not visible in the current code.
Included today
HTTP API clients inside app modules such as WooCommerce and e-conomic
Inbound webhook controllers for external systems pushing updates back into Indexed PIM
Feed endpoints that can require bearer-token authorization
Messenger-based background processing for long-running sync work
Per-app API logs with payloads, status codes, events, and timing
How integrations are exposed
The current architecture favors app-specific API modules over one monolithic API layer.
Outbound API Clients
App services assemble requests to third-party REST APIs, submit them with the configured credentials, and write structured log records for each call.
Inbound Webhook Endpoints
Controllers such as the e-conomic and Rackbeat webhook handlers accept external POST requests, validate secrets, and trigger sync handlers back into the PIM.
Queued Sync Messages
Entity events dispatch Messenger messages instead of doing all HTTP work inline, which keeps app workflows responsive during imports and exports.
Download and Import Actions
Integration apps expose actions for downloading customers, products, orders, categories, and related master data from external services into Indexed PIM.
Feed Delivery Endpoints
The feed app provides public routes that can validate bearer tokens before generating output, which is useful for controlled machine-to-machine exports.
Operational Logging
The `ApiLog` entity stores request payloads, response payloads, events, response times, and status codes for supported app integrations.
Typical request flow
The same pattern shows up across multiple integrations in the repository.
Store app credentials and configuration
Each app keeps its own connection settings such as shop URL, consumer key, secret, token pair, or webhook secret depending on the service being integrated.
Trigger a sync or receive a webhook
Actions pages can queue uploads and downloads, while event subscribers and webhook controllers can start the flow automatically when data changes.
Send or process API data in the background
Messenger handlers and action services perform the actual API work, translate remote data, and map it onto products, customers, orders, and related records.
Review logs and queue state
Supported apps expose API log screens and queue counts so teams can inspect payloads, failures, and timing without digging through server logs.
Current implementation note
This feature page reflects the integration APIs implemented in app modules. If you are looking for a public, platform-wide REST developer product with universal CRUD endpoints, I did not find that module in the current repository.
Need API-based integrations tied to your PIM workflows?
Use Indexed PIM’s app integrations, queues, webhook endpoints, and logs to connect commerce, ERP, accounting, and export flows without building everything from scratch.