# Getting Access to Stage and Production

> RAZE sets you up in two environments, Stage for testing and Production for live orders, each with its own service account.

Product: RAZE Developer Portal
Source: https://getaraze.com/tools/api-stage-and-production-access
All guides: https://getaraze.com/tools

## Quick Reference

- Build and test every call in Stage first.
- Keep each environment's API address, codes and service account together.
- Use the Stage service account only in Stage, and the Production one only in Production.
- Store service account passwords where only your integration team can read them.

## Before You Start

- Your institution is working with RAZE on an API integration.
- You know who on your team will hold the service account passwords.

## Step 1: Know the Two Environments

**Stage.** Stage is a real sandbox with its own address and credentials. Stage orders never reach a live inspector and nothing is billed, so test as often as you need. Your Stage credentials can also complete a sample residential draw inspection, so you can test the whole flow.

**Production.** Production is live: every order goes to a real inspector. Move to Production only after your full flow works in Stage (see Going Live in Production).

## Step 2: Collect Your Setup Details

**One service account per environment.** RAZE gives you a service account for Stage and another for Production. Your system uses it to request access tokens.

**API address and institution codes.** Each environment has its own API address and its own institution codes, which your create calls carry. The API reference in the Developer Portal shows the server for the environment you sign in to.

**Passwords come separately.** Service account passwords are delivered separately from the rest of your setup details.

## Step 3: Protect the Credentials

**Restrict access.** Keep the passwords where only the people who run the integration can read them. If a password is exposed, ask RAZE to reset it.

## Tips

**DO**
- Label every setting by environment so Stage and Production values never mix.
- Test each call in Stage before you order in Production.
- Ask RAZE for a reset as soon as a password may be exposed.

**WATCH FOR**
- A Stage service account doesn't work in Production, and a Production one doesn't work in Stage.
- Production calls never go to the Stage address.
- Your Developer Portal sign-in is your own RAZE account, not the service account.

## Troubleshooting

**Q: Are Stage orders billed?**
A: No. Stage orders never reach a live inspector and nothing is billed.

**Q: Can we use one service account for both environments?**
A: No. Stage and Production each have their own service account and password.

**Q: A password was exposed. What now?**
A: Contact RAZE and ask for a reset, then update the password in your system.

## Need Help?

Email RAZE support at contact@getaraze.com, or send a support request from https://getaraze.com/tools.