ILGFUSE

Authentication

Every request to Fuse is authenticated with HTTP Basic — no tokens to refresh, no signing, nothing exotic.

Your credentials

The username is your businessId and the passwordis your API key. Both arrive in your onboarding pack — if you don't have them yet, ask your ILG integration contact.

# Username is your businessId, password is your API key
curl -X POST 'https://api.integrations.fuse.ilg.software/api/v2/sales-orders' \
  -u "$FUSE_BUSINESS_ID:$FUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-binary @sales-orders.json

There's nothing bespoke underneath — any HTTP client's built-in Basic auth support works:

# What actually rides the request — standard HTTP Basic
Authorization: Basic base64(businessId:apiKey)

One business per key

Your key acts for your business only. Every record you send must carry your own businessId (product.identifiers.businessId for master data) — a record for a different business is rejected with a 400.

When it goes wrong

  • 401Missing or wrong credentials — check the businessId and key against your onboarding pack.
  • 400Authenticated fine, but a record in the body belongs to a different businessId than the one you authenticated as.

Keep the key server-side

Treat the API key like any other production secret: call Fuse from your backend, never from a browser or mobile app, and keep it out of source control. If a key is ever exposed, contact your ILG integration contact to rotate it.

Trying things out

The sandbox at https://sandbox.api.integrations.fuse.freightops.dev mirrors every endpoint and accepts any credentials, so you can develop against it before your real key arrives — the Try it console on each endpoint page uses it. Never point tests at production, and never paste your production key into a web page.

Environments

  • ProductionCreates real orders

    Live. A record sent here reaches the warehouse floor and is picked, packed and despatched.

  • DevelopmentReal pipeline, test data

    The full Fuse pipeline against a test warehouse. Use it for end-to-end runs once the sandbox is happy.

  • SandboxNothing is created

    A mock of every endpoint. Validates the shape of your payload and accepts any credentials — build against this first.