Connector name: Recurly

Table name: plan_currency_history

Column to add: price_segment_id (Column exists already, need to add as primary key)

API documentation link:  https://recurly.com/developers/api/v2021-02-25/index.html#operation/get_plan 

Additional details:

Description: The Recurly connector's plan_currency_history table uses plan_id, plan_updated_at and currency as its primary key. price_segment_id is already a column in the table, but it isn't part of the key.

In Recurly, a plan can have several prices in the same currency: one base price plus one price for each price segment. The Fetch a plan endpoint returns all of them in currencies[], each with its price_segment_id and price_segment_code. In the table, all of a plan's prices in one currency share the same key values, so each overwrites the previous one and only one row per plan and currency is kept. The row kept can be a regional segment price rather than the base price.

On our sandbox site, each paid plan has 280 prices in Recurly: 32 base prices (one per currency) and 248 regional segment prices. The table holds 64 rows in total. For some plan and currency pairs, the row it keeps is a segment price, so the table doesn't reliably show the base price either.

Request: add price_segment_id to the primary key of plan_currency_history, so that every plan × currency × price segment price is kept as its own row.

Impact: we're moving our subscription billing to Recurly and use price segments for regional pricing. Without this change, we can't report on plan prices by region or price segment from the connector, including checking what a subscriber was charged against the price list. Today we'd have to call the Recurly API separately to get the full price list.

Related support ticket: #427993