What connects today, stated exactly.

Integration today is through the HTTP API and CSV exports.

• The HTTP API is documented endpoint by endpoint, with who may call it and the body it takes. The documentation is provided on request.
• CSV exports cover orders, invoices, payments, bids, spend, savings and the audit trail.
• Every export and every API call is limited by the caller’s role and organisation, the same as the screens.

There are no packaged ERP connectors. A connector is a separate scoped service.

• A connector for one ERP system is a separate scoped service on every plan, quoted after a review of your data: supplier identifiers, cost centres, purchase orders, receipts, invoices, tax codes and payment status.
• Self-service API credentials with webhooks are planned for the Enterprise plan and are not available yet.

The commercial registration check is not live. No supplier's registration has been checked against the registry. The platform operator reviews the documents a supplier uploads and records the outcome. This is a document review by a person, not a registry check.

• The label "Commercial registration checked" with a date appears in the application only where live evidence exists.

ZATCA e-invoicing is not available. Invoices carry the tax-invoice fields and totals by tax category on the platform; nothing is transmitted to ZATCA.

Financing, insurance, identity and electronic-signing services are not part of any plan. They would be offered only through separately approved partners, with their own terms and fees disclosed.