Skip to main content
The Partner API has two environments. Use development for integration work and switch to production once you’ve signed off.
EnvironmentBase URLPurpose
Developmenthttps://api.dev.shadowchef.co/v1/partnerIntegration, QA, ongoing testing. Use this as your sandbox.
Productionhttps://gateway-enterprise.klikit.io/v1/partnerLive restaurant traffic.

​
Why there’s no separate sandbox

We deliberately use the development environment as the sandbox. That way fixtures stay realistic, the data shapes match production exactly, and you catch breaking changes the moment they ship — not on your go-live day. You’ll get a separate credential per environment from your klikit operator. Dev credentials never work in production and vice versa.

​
Switching between environments

Keep the base URL, the API key, and the API secret in your environment config — not hard-coded. A typical layout: 
# .env.dev
PARTNER_BASE_URL=https://api.dev.shadowchef.co/v1/partner
PARTNER_API_KEY=...
PARTNER_API_SECRET=...

# .env.prod
PARTNER_BASE_URL=https://gateway-enterprise.klikit.io/v1/partner
PARTNER_API_KEY=...
PARTNER_API_SECRET=...
Your code should never branch on environment — only on the values it reads from config.

​
Webhook URLs

Webhook registrations live per environment too. Your dev receiver URL gets events from dev orders; your prod receiver URL gets events from prod orders. Don’t point both at the same endpoint unless you have a way to separate the streams downstream.