Borong API & Webhooks: Custom Integration for Any Architecture
Standard integration protocols like cXML Punchout and native ERP connectors cover the majority of enterprise procurement integration needs. For organisations with bespoke system architectures, custom applications, or integration requirements that fall outside the standard connector library, Borong provides an open API and webhook support that enable custom integration between Borong and any connected system.
When to Use the Borong API
The API is the right integration when requirements go beyond what standard connectors provide: connecting procurement data to a proprietary or custom-built ERP, building workflows that extend Borong's standard capability, feeding business intelligence and analytics platforms, automating supplier management or catalog updates, and developing internal applications that consume Borong data programmatically.
What the Borong API Covers
The Borong REST API provides programmatic access to core platform resources including catalog and product data, purchase requisitions and orders, supplier records, spend and analytics data, user and organisation management, and approval workflow status. API responses are returned in standard JSON format. The API is versioned and documented to support stable integration development. Full API documentation is available to authenticated developers and integration partners.
Webhooks: Event-Driven Integration
Webhooks push data to connected systems when specified events occur. Rather than polling the API, a connected system receives a notification payload when an event fires: a purchase order approved, a delivery confirmed, a supplier invoice received. That cuts latency and API call overhead where near-real-time propagation is required.
Webhook endpoints are configured within the Borong platform and can be secured with signing secrets to verify the authenticity of incoming payloads. Supported events and payload formats are documented in the API and webhook reference.
Authentication and Security
The Borong API uses OAuth 2.0 for authentication. API keys are issued per integration and scoped to the specific resources and operations required. All API communication is over HTTPS with TLS encryption. Rate limiting applies to prevent abuse and ensure platform stability for all users. Enterprise integrations requiring dedicated API capacity can discuss custom rate limit arrangements with the Borong integration team.
Who the API Is Built For
The API is built for developer and IT teams inside enterprise organisations, and for integration partners building custom connections. It also suits organisations whose business intelligence platform or data warehouse needs to ingest Borong spend data for consolidated reporting.
Build on the
Borong API
Speak with an integration specialist about API access, sandbox environments, and webhook configuration for your custom architecture.