Developer portal

Build growth workflows with integrations, exports and the FiveX REST API.

Use developer-first resources to connect marketplace data to internal tools, BI and partner systems, without fragile screen scraping or duplicate pipelines.

Book a demo OAuth integrations

Getting started paths

Guides & onboarding

Map your stack to FiveX entities, tenancy and rollout, so engineering, finance and marketplace teams share the same plan.

Book a demo

Integrations & OAuth

Ship connector flows with refresh, retry and revocation patterns hardened in production multitenant environments.

Integrations hub

Data & exports

Pair REST for operational workflows with scheduled exports when finance and BI need warehouse-scale datasets.

Explore exports
Technical resources

Find the guidance you need

Pick a path that matches your build: API access, OAuth connectors, exports, security context and commercial packaging.

API

Programmatic KPIs and alerts

Wire dashboards, notifications and internal tools to the same entities operators see in the FiveX cockpit.

View OAuth

Marketplace credential flows

Centralise consent, token refresh and connector defaults instead of maintaining bespoke scripts per channel.

View Exports

Warehouse-ready datasets

Keep BI models honest with repeatable exports while APIs handle transactional actions.

View Product

Analytics & SKU economics

See how portal models map to API resources for faster, safer integration work.

View Security

Data security & governance

Share how isolation, auditing and revocation work when procurement reviews your stack.

View Plans

Plans and API scope

Match exports, connectors and API access to the markets and teams you operate today.

View
API FAQ

Questions about the FiveX REST API

What can developers build with the FiveX API? Developers can use FiveX data for alerts, dashboards, internal tools and automation.

The API gives teams a way to use marketplace, product, performance and operational data outside the FiveX interface. Common use cases include internal dashboards, reporting workflows, alerts and partner processes.

Is the API meant to replace exports? No, exports and API access solve different data needs.

Scheduled exports are useful for BI and reporting datasets. API access is better for workflows that need programmatic access, custom tools or more direct automation.

Who should use API access? API access is best for teams with developers or data teams that want to extend FiveX.

If your company wants to connect FiveX data to internal systems, automated alerts, partner tooling or custom dashboards, API access can make the cockpit part of a broader operating stack.

Architecture d’abord ou proposition commerciale ?

Envoyez votre mix canaux, nous montrons connecteurs, stratégie de sync et onboarding.

Book a demo OAuth integrations