Home / API

API access designed around your own SureISP data layer

Customers authenticate to your site, spend from your own wallet system, and receive SureISP order records while supplier API calls stay on the server.

Customer-facing model

What the portal exposes

SureISP account authentication for each customer
SureISP wallet balance stored in your own data store
SureISP order history scoped to the signed-in user
SureISP-side fulfillment status after supplier handoff

Server-side model

What stays hidden

Supplier API key and supplier base URI details
Supplier master-account balance and payment methods
Unrelated supplier orders and IP inventory from other customers
Supplier auth / whitelist objects that do not belong to the signed-in SureISP user

Order lifecycle

The billing and ownership boundary now sits at the SureISP layer.

1. Customer signs up on your SureISP site
2. Customer wallet balance is stored in your own database
3. Customer creates a SureISP order
4. SureISP wallet is charged first
5. Server sends the supplier order using your supplier API key
6. SureISP stores the mapping between local order and supplier order
7. Customer sees only SureISP order data in the portal

Recommended endpoint groups

Expose your own stable SureISP API and keep the supplier API behind it.

Accounts: sign in, profile, SureISP wallet balance
Checkout: quote a product, create a SureISP order, inspect order state
Orders: list only the current customer's SureISP orders
Fulfillment: show mapped IP or credential data only for the current customer order
Billing: expose SureISP wallet ledger rows instead of supplier account funding details