# General Information

The FunnelFlux Pro API is available to active FunnelFlux Pro users. It covers authentication, asset management through the ledger service, custom domain management, reporting, and log/update workflows.

Base URL:

```text
https://api.funnelflux.pro/v1
```

If you find an error in these docs or while using the API, contact FunnelFlux support with the endpoint, request payload, response, and approximate request time.

## Start Here

- Read [Authentication](/authentication) before making requests.
- Read [Generating Asset IDs](/id-generation) before creating any asset, funnel, node, page group, condition, or related ledger record.
- Read [API Best Practices](/best-practices) before automating reporting or high-volume workflows.
- Read [Webhook Payloads](/webhooks) when receiving outbound flow webhook requests from FunnelFlux Pro.
- Read [Middleware Nodes](/middleware) when building synchronous routing decisions with external systems.
- Use the API reference for request and response details:
  - [Authentication API](/api/auth)
  - [Domains API](/api/billing)
  - [Ledger API](/api/ledger)
  - [Reporting API](/api/reporting)

## Important Limitations

- Asset IDs must use the FunnelFlux ID format. Do not generate arbitrary IDs. Some analytics columns have strict ID length/type expectations, and invalid IDs can break reporting.

- Some legacy ledger endpoints still use "campaign" in the URL. In FunnelFlux Pro UI language, these usually refer to funnel groups, not URL tracking field campaigns.

- Funnel creation is possible through the API, but it is easy to create invalid references. Create simple examples in the UI first and inspect the request order before automating funnel creation.

- The `meta` object on some assets is used internally for versioning and validation. Do not use it for notes or custom application data.

- FunnelFlux may limit or suspend API access for abusive or unsafe automation, including excessive asset generation, unnecessary minute-by-minute updates, or reporting workloads that degrade service for other users.

- A `429` response means your integration has been temporarily rate limited. Back off before retrying.