Environments

Stage (UAT) vs Live (Production)

Same credentials, different hostnames

Your API Key and App ID are the same across both environments. To switch, change only the hostname in your request:

- https://uat-ext.signcare.io/api/v1/pan/verify
+ https://ext.signcare.io/api/v1/pan/verify

This keeps your integration code clean — a single BASE_URL environment variable in your app is all you need.

Recommended setup in your application

Use an environment variable so your deploys control which SignCare environment you hit:

# .env.development
SIGNCARE_BASE_URL=https://uat-ext.signcare.io
 
# .env.production
SIGNCARE_BASE_URL=https://ext.signcare.io

Example (Node.js):

const SIGNCARE_BASE_URL = process.env.SIGNCARE_BASE_URL;
 
async function verifyPan(pan) {
  const res = await fetch(`${SIGNCARE_BASE_URL}/api/v1/pan/verify`, {
    method: 'POST',
    headers: {
      'X-API-KEY': process.env.SIGNCARE_API_KEY,
      'X-API-APP-ID': process.env.SIGNCARE_APP_ID,
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({ pan, consent: 'Y', consent_text: '...' })
  });
  return res.json();
}

What's different between stage and live

• Stage rate limits are relaxed — you can test without hitting 429s during development.
• Stage does not charge against your billing usage.
• Stage webhooks are delivered normally — use this to test your callback handlers.
• Stage does not guarantee data retention beyond 7 days.

Going live checklist

Before switching your production app to ext.signcare.io:

1. ✅ Confirm your API Key is enabled for Production (contact your account manager).
2. ✅ Whitelist SignCare's webhook source IPs in your firewall (see Webhooks).
3. ✅ Confirm your billing agreement covers expected volume.
4. ✅ Verify you handle all documented error codes gracefully.
5. ✅ Run a smoke test against Live with a small batch before full rollout.