ReliApply Sandbox Onboarding

Use the ReliApply sandbox environment to review available API endpoints, retrieve sandbox credentials, and begin testing supported ReliApply API workflows.

The sandbox is intended for approved Partner and ISV users during the early ReliApply rollout. Access is currently limited, manually provisioned, and restricted to non-production testing.

Getting Started

Early partner onboarding follows a manual approval process.

1. Request sandbox access

Your organization must be approved by ReliaFund before sandbox access is granted.

Once approved, ReliaFund will create or enable your Developer Portal account and assign access to the ReliApply Sandbox API product.

2. Sign in to the Developer Portal

After your account has been provisioned, sign in to the Developer Portal using the account provided during onboarding.

Once signed in, you will be able to access the ReliApply Sandbox API details page.

The API details page includes:

  • Available endpoint definitions

  • Required request headers

  • Request body schemas

  • Response models

  • Example responses, where available

  • An interactive test console for supported routes

The test console is already connected to the ReliApply sandbox environment.

3. Retrieve your sandbox subscription key

Your sandbox API access is controlled through an Azure API Management subscription key.

After signing in:

  1. Open your Developer Portal profile.

  2. Locate your ReliApply Sandbox subscription.

  3. Copy your primary or secondary subscription key.

  4. Use the key when testing API routes from the API details page or from your own API client.

Use the following header when calling the ReliApply sandbox API:

Ocp-Apim-Subscription-Key: {your-sandbox-subscription-key}

Keep your subscription key private. Do not share it outside your organization. If a key is exposed, contact ReliaFund so it can be regenerated or replaced.

4. Review the API details page

The ReliApply Sandbox API details page works similarly to an interactive Swagger page.

Use it to review endpoint definitions, inspect request and response models, and test available routes directly against the sandbox environment.

Because the test console is connected to the sandbox backend, requests submitted from the API details page are treated as sandbox test requests.

5. Begin testing sandbox workflows

Once you have access to the ReliApply Sandbox API product and your subscription key, you can begin testing supported workflows.

Recommended first steps:

  1. Open the ReliApply Sandbox API details page.

  2. Select an available endpoint.

  3. Review the required headers, parameters, and request body.

  4. Enter test values into the request fields.

  5. Submit the request using the built-in test console.

  6. Review the response status code and response body.

  7. Capture the request ID or correlation ID when reporting issues.

You may also test the API using Postman, Insomnia, curl, or another API client.

Example request headers:

Ocp-Apim-Subscription-Key: {your-sandbox-subscription-key} 
Content-Type: application/json

Sandbox Access Only

All credentials issued during this phase are for sandbox testing only.

Sandbox credentials must not be used for production traffic, real customer onboarding, live payment-processing activity, or production data submission.

Unless ReliaFund provides separate written guidance, all sandbox testing should use test data only.

Current Rollout Limitations

ReliApply is currently in an early rollout phase. Some features and workflows may be incomplete, restricted, or subject to change.

Current limitations may include:

  • Access is manually approved by ReliaFund.

  • Developer Portal accounts are manually provisioned.

  • Sandbox credentials are manually assigned.

  • The API details page is connected to the sandbox environment only.

  • Sandbox access does not imply production access.

  • Production credentials are not currently self-service.

  • Available endpoints may change as development continues.

  • Some workflows may be unavailable, partially implemented, or limited to specific partner testing scenarios.

  • Request validation, response formats, and error handling may change before production release.

  • Rate limits and access policies may be adjusted during sandbox testing.

ReliaFund will communicate material changes that impact partner testing.

Support

For sandbox onboarding, credential issues, API details page questions, or testing support, contact ReliaFund.

When reporting an issue, include as much of the following as possible:

  • Partner or ISV name

  • Developer Portal account email

  • API endpoint being tested

  • Approximate date and time of the request

  • Request ID or correlation ID, if available

  • HTTP response status code

  • Summary of the issue

  • Whether the request was made from the Developer Portal test console, Postman, or another API client

ReliaFund will review the issue and provide guidance based on the current sandbox rollout state.