We are using drupal/recurly as the front end for our users to manage their accounts. But ultimately the status of their account is validated by our PC client software. The software uses the Recurly API and the Drupal services +services views module (REST server).
In order to accurately match up the accounts between Drupal and Recurly, we are interested in getting the data found in drupal_recurly_account table to be exposed via the REST server. If it was available to the “views” then we could then expose that view in that manor.
Maybe this is already possible and I'm missing it.
We did assume that user-xx where “xx” is equal to the entity id. But maybe that assumption doesn't work in all cases. I feel like maybe dotting our i's and crossing our t's by relying on the actual data would be smart.
IN_PROGRESS / Accepting payments