Integrations / Recurly
Recurly
Recurly subscription billing and revenue management platform for accounts, plans, subscriptions, invoices, transactions, and coupons.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
In Telara
Connect in Telara
Recurly API key over HTTP Basic Auth. Use the API key as the username and leave the password blank (or any placeholder value — it is ignored). Confirmed against the spec's components.securitySchemes.api_key entry, which declares type http and scheme basic — not a bearer/header token scheme, despite the "api_key" name. Same shape as this catalog's dropbox_sign.yaml connector; see that file's auth block for the identical pattern. Keys are managed from the site's API Credentials page.
In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.
- API key
- Password
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Account | Partial — not every record the vendor holds is synced |
| Invoice | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Account | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
| Invoice | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Account, Invoice.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty