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

# Get started

> Configure and deploy the Prove Connector with Grand Central

Complete the following prerequisites and configuration to start using the Prove Connector.

## Prerequisites

Before you begin, make sure you meet the following requirements:

* You have completed the steps in the [Get started](/connectors/getting-started).
* You have an active contract with Prove and have configured your accounts and credentials for Prove.

## Configuration

To configure your connector, follow these steps:

1. Set your APIM subscription key in the header as follows:
   * Key: `api-key`
   * Value: `<your subscription key>`
2. Request the Grand Central team to set up a connection with Prove, and provide the following details for OAuth token generation:
   * `prove-grant-type`
   * `prove-password`
   * `prove-username`
3. Configure the Prove `baseURL` in the `gc-applications-live` repository in the connector’s `values.yaml` file:

```json theme={"system"}
prove.baseUrl= //PROVE environment base URL
```

4. The following example shows the connector’s `values.yaml` file location:

```
├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            ├── gc-prove
              └── party-lifecycle-v0.values.yaml
              └── party-v0.values.yaml
              └── party-v2.values.yaml
```

## Test your integration

To access the Party Reference Unified API, include your Grand Central subscription key in the request header. If you don't have a key, contact the Grand Central Support Team to have one provisioned.

| Key       | Value                     |
| :-------- | :------------------------ |
| `api-key` | `<your_subscription_key>` |

Test the API using the [Postman collection](https://github.com/bb-ecos-ecos/grandcentral-documentation/blob/main/Postman-Collection/GC%20Party%20Lifecycle%20-%20Unified%20Spec.postman_collection.json).

## Troubleshooting

If your connector isn't responding as expected, check these common scenarios.

<AccordionGroup>
  <Accordion icon="lock" title="5xx: internal server error or core system down">
    **Cause:** The Grand Central gateway can't establish a handshake with the Prove endpoint. This typically indicates an upstream service outage at Prove or a network routing failure.

    **Solution:** Verify the operational status of the Prove environment with Prove. If the service is operational, contact the [Grand Central team](mailto:gc_support@backbase.com) team.
  </Accordion>

  <Accordion icon="wifi-slash" title="5xx: timeout or sockettimeoutexception">
    **Cause:** The request to Prove exceeded the configured timeout threshold. This can occur during high load or network latency issues.

    **Solution:** Verify the operational status of the Prove environment with Prove. If the service is operational, contact the [GC Support](mailto:gc_support@backbase.com) team to review timeout configurations.
  </Accordion>

  <Accordion icon="key" title="Invalid authentication">
    **Cause:** The credentials provided during setup are incorrect.

    **Solution:** Verify your credentials with Prove and contact the GC team to update the connection.
  </Accordion>

  <Accordion icon="gauge-high" title="429: rate limit exceeded">
    **Cause:** The number of incoming requests exceeded the defined threshold for your subscription tier. This response protects the stability of the Grand Central and partner infrastructure.

    **Solution:** Review your application's request patterns to identify unexpected spikes. If you require higher throughput, contact the Grand Central team to request an adjustment to your APIM rate limit policy.
  </Accordion>
</AccordionGroup>

## Need more help?

<Card icon="envelope" href="mailto:support@grandcentral.io" title="Contact support">
  Reach out to the Grand Central team for assistance with environment setup or rate limit increases.
</Card>