feat(integrations): add support for BeeTexting

[LevSky22]

API

BeeTexting Connect API: https://developer.beetexting.com/

Authentication model

BeeTexting uses OAuth 2.0 Authorization Code together with a separate API key issued for the same API Connect application:

• Client ID and Client Secret configure the OAuth application in Nango.
• Access and refresh tokens belong to each authorized connection.
• The application API key must be added to every provider API request as X-API-Key alongside the OAuth bearer token.

This is not an alternative API-key authentication mode. Both credentials are required simultaneously.

Proposed provider template

• Provider key: beetexting
• Category: communication
• Auth mode: OAUTH2
• Authorization URL: https://auth.beetexting.com/oauth2/authorize/
• Token/refresh URL: https://auth.beetexting.com/oauth2/token/
• Proxy base URL: https://connect.beetexting.com/prod
• Grant: Authorization Code
• PKCE disabled for this provider flow
• No explicit scope parameter; BeeTexting assigns permissions to the API Connect application
• Secret integration field: apiKey
• Proxy header: x-api-key: ${integrationConfig.apiKey}

Organization and Department IDs used by some message/webhook paths are routing identifiers, not credentials. The connection guide will explain where to obtain them without adding them to every Proxy request.

Provider-specific request behavior

BeeTexting's API gateway can reject a bodyless POST when it is serialized as form-encoded. The tested provider configuration declares proxy.body: {} so Nango sends an empty JSON object only when the caller did not supply a body.

Contribution contents

• Provider definition
• BeeTexting logo
• Quickstart documentation
• OAuth/API Connect setup and connection guide
• Generated provider documentation indexes

Validation completed

• OAuth authorization and refresh succeeded on self-hosted Nango.
• Nango Proxy materialized both the bearer token and protected X-API-Key.
• SMS and MMS canaries succeeded.
• Provider-schema validation passes.

Depends on the generic Proxy/UI support proposed in #6881.

Official references:

• https://developer.beetexting.com/oauth-2-0-for-beetexting-1578529m0
• https://developer.beetexting.com/faq-1623165m0
• https://developer.beetexting.com/create-or-update-subscription-21352087e0

[linear-code]

NAN-6417