---
title: "Environments"
description: "AgentSync offers two environments for API integration:"
url: "https://developer.agentsync.io/api-environments"
image: "https://developer.agentsync.io/_og/d/c_Ocean.takumi,title_Environments,description_~QWdlbnRTeW5jIG9mZmVycyB0d28gZW52aXJvbm1lbnRzIGZvciBBUEkgaW50ZWdyYXRpb246,props_eyJ0aGVtZSI6eyJtb2RlIjoibGlnaHQiLCJjb2xvcnMiOnsicHJpbWFyeSI6IiMxODdFRkYifX19,p_Ii9hcGktZW52aXJvbm1lbnRzIg,s_vCtcIdoial1rvUzW.png"
---

# Environments

AgentSync offers two environments for API integration:

-   **Production** – for live data access and real transactions
-   **Sandbox** – for development, testing, and integration validation

---

## [Production Environment](#production-environment)

The Production environment is used for live integrations and should only be used when your application is production-ready.

-   **Billing**: All requests are billed according to your plan
-   **Data**: Responses contain real producer data from the NIPR system
-   **Reliability**: Full system availability and support

> Use the Production environment only after completing testing in the Sandbox.

---

## [Sandbox Environment](#sandbox-environment)

The Sandbox environment is a safe place to develop, test, and debug your integration without incurring costs or accessing live data. All AgentSync APIs — ProducerSync, Contracting, Hierarchies, and Identity — are available in sandbox under the `*.sandbox.agentsync.io` base URLs (see [API Base URLs](https://developer.agentsync.io/api-base-urls)).

For ProducerSync, the sandbox uses scrambled production data sourced from **NIPR Beta**, creating realistic—but obfuscated—responses.

### [Sandbox Test Data for Contracting, Hierarchies & Identity](#sandbox-test-data-for-contracting-hierarchies-identity)

Your sandbox account for these APIs **starts empty**. There is no seeded data, so your first list call correctly returns an empty page:

```json
{ "items": [], "page": { "size": 0, "nextToken": null } }
```

That is a successful response, not a broken integration. How you populate it depends on the API:

| API                       | How test data is created                                                         |
| :------------------------ | :------------------------------------------------------------------------------- |
| Identity                  | Via the API — identity.profiles.write grants POST /v2/persons, firms, addresses, phones, and bank accounts |
| Contracting & Hierarchies | Not via the v2 API — the entire v2 surface is read-only. Carriers, products, commission levels, and assignments must be created in the AgentSync application by a user with sandbox access |

> **Request sandbox application access alongside your API credentials.** Because Contracting and Hierarchies test data has to be built in the UI, ask [support@agentsync.io](mailto:support@agentsync.io) for application logins at the same time as your OAuth client — otherwise you'll have working credentials and nothing to read. Note these are three distinct kinds of access: any existing single sign-on covers application login only, the OAuth client covers API access, and sandbox application access is separate again.

-   **No billing** – free to use for development and QA
-   **Scrambled data** – realistic structure, but not tied to real individuals
-   **Lag in new data** – recently issued NPNs may not appear immediately
-   **Privacy note** – Even though data is scrambled, fields like `address` should still be handled in accordance with your organization's data privacy policies

> The Sandbox is **not** intended for validating data accuracy, completeness, or freshness.