Bitly

Bitly is a link management platform that lets you harness the power of your links by shortening, sharing, managing and analyzing links to your content.

In order to integrate Bitly with Relyance AI you will need a Client ID and Client Secret.

In Bitly:

1. Login to your Bitly account.
2. In the left-hand navigation menu click Settings.
3. This will open the Setting sub-menu, under the Developer settings section click API.
4. Click the Register new app button.
5. Fill out the Register OAuth application form: Application name: Provide a meaningful name (e.g. Relyance Scan) Application link: https://www.relyance.ai Redirect URIs: https://root.relyance.ai/api/oauth2 Application description (optional): Provided a meaningful description
6. Click Save.
7. Copy the Client ID and Client Secret to be used in Relyance.

In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the Settings Menu in the bottom left-hand side.
3. Select Integrations.
4. Click on the Vendor Integration tab.
5. Find the Bitly integration card and click it to open its connections.
6. Under Authentication Method, choose Oauth2 / App Token.
7. Paste the Client ID and Client Secret into their respective fields.

9. Click Authenticate.
10. This will bring you to the Bitly authorization page. Click Allow.

11. At this point, you should see the following result on the Vendor Integrations page:

12. Congratulations, you are now connected to Bitly.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. Authorised, then empty. The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
2. A credential rotated at the vendor is not picked up here. Client Secret is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

The OAuth (browser authorization) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example bitly/<connection_id>) or reading it with the relyance_integration_connection data source.