> ## Documentation Index
> Fetch the complete documentation index at: https://docs.billsentry.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Sandbox & Support

> Testing environment details, security requirements, and support contacts.

## Sandbox environment

A sandbox environment is available for integration testing before production deployment. BillSentry will provide separate credentials for sandbox — these are fully isolated from production and must not be mixed.

| Item                       | Details                                                                          |
| -------------------------- | -------------------------------------------------------------------------------- |
| Sandbox Client ID & Secret | Separate M2M credentials — do not use production credentials in sandbox          |
| Sandbox API Key            | A distinct `x-api-key` value                                                     |
| Sandbox Endpoint URL       | Same endpoint as production — your API key routes you to the correct environment |
| Sandbox Token URL          | Same token URL as production                                                     |

<Info>
  All sandbox requests are isolated from production. No production records are created or modified. Usage logged against sandbox credentials does not count toward production billing.
</Info>

<Info>
  For step-by-step instructions on testing with Postman, including how to handle the gzip requirement and sample payloads, see [Testing with Postman](/postman).
</Info>

***

## Sample test payloads

Use these payloads to verify your integration end-to-end before sending real bill data.

### Institutional — CA Inpatient (DRG 473)

A California inpatient hospital bill. Tests DRG-based pricing, Medicare treatment flag, and late fee handling.

```json theme={null}
{
  "Bill": {
    "UniqueID": "3",
    "ControlNumber": 2080,
    "ProviderType": 2,
    "ZipCode": "93291",
    "ZipPlusFour": "93291",
    "BillReviewState": "CA",
    "JurisdictionState": "CA",
    "MedicareNumber": "050057",
    "DRG": "473",
    "ClaimsOfficeReceivedDate": "2025-07-15T00:00:00",
    "ProcessedDate": "2025-07-15T00:00:00",
    "AdmitDate": "2025-07-15T00:00:00",
    "DischargeDate": "2025-07-15T00:00:00",
    "ProviderTaxID": "123456789",
    "BucketList": []
  },
  "BillOptions": {
    "IsLateFee": true,
    "IsMedicareTreatment": true,
    "IsIgnoreTimelyFiling": true
  },
  "Services": [
    {
      "Line": 1,
      "CPT1": "120",
      "CPT2": "",
      "ServiceDate": "2025-07-15T00:00:00",
      "QuantityBilled": 1.0,
      "POS": "21",
      "Charge": 2316.25,
      "BucketList": [],
      "ControlNumber": 2080
    }
  ],
  "Claim": {
    "DisplayID": "123-123",
    "State": "CA",
    "ZipCode": "92882",
    "StateOfJurisdiction": ""
  },
  "Provider": {
    "TaxID": "123-123",
    "PracticeState": "CA",
    "PracticeZipCode": "",
    "BillingZipCode": ""
  },
  "BillHistory": []
}
```

### Professional — CA Physician (CMS-1500)

A California physician office visit. Tests professional fee schedule pricing.

```json theme={null}
{
  "Bill": {
    "ControlNumber": 1001,
    "ProviderType": 1,
    "ZipCode": "90210",
    "BillReviewState": "CA",
    "JurisdictionState": "CA",
    "ProviderTaxID": "123456789",
    "BucketList": []
  },
  "BillOptions": {
    "IsLateFee": false,
    "IsIgnoreTimelyFiling": false
  },
  "Services": [
    {
      "Line": 1,
      "CPT1": "99213",
      "CPT2": "",
      "ServiceDate": "2025-07-15T00:00:00",
      "QuantityBilled": 1.0,
      "POS": "11",
      "Charge": 175.00,
      "BucketList": [],
      "ControlNumber": 1001
    }
  ],
  "Claim": {
    "DisplayID": "CLM-001",
    "State": "CA",
    "ZipCode": "90210",
    "StateOfJurisdiction": "CA"
  },
  "Provider": {
    "TaxID": "123456789",
    "PracticeState": "CA",
    "PracticeZipCode": "90210",
    "BillingZipCode": ""
  },
  "BillHistory": []
}
```

***

## Transport and security requirements

* All requests must use **HTTPS**. HTTP is not supported.
* Minimum TLS version: **1.2**
* Never include your `client_secret` in client-side code, version control, or log files
* Rotate your `client_secret` immediately if you believe it has been compromised, contact BillSentry support

***

## Support

| Need                              | Contact                                                         |
| --------------------------------- | --------------------------------------------------------------- |
| Request sandbox access            | [billsentry.com/developers](https://billsentry.com/developers/) |
| Integration questions             | Contact your BillSentry integration engineer                    |
| Production incidents              | Include the `x-request-id` from the failed response             |
| Credential rotation or revocation | Contact BillSentry support immediately                          |