@OmarAlmonte, another one to add to the tracker.
The Subscriptions - List Subscriptions endpoint is missing the Contact First Name, Last Name, and Email Address fields.
https://developer.infusionsoft.com/docs/restv2/#tag/Subscriptions/operation/listSubscriptions
This is supplied in the XML-RPC “RecurringOrderWithContact” table plus several other contact fields.
https://developer.infusionsoft.com/docs/table-schema/#RecurringOrderWithContact
I can also search by Name and Email as well.
Hi Pav, this is by design. The REST API keeps subscriptions and contacts as separate resources, so contact fields such as name and email are not included in the subscription resource.
If you need contact details, you can use the contact_id returned by the List Subscriptions endpoint and retrieve the corresponding contact through the Contacts endpoint.
I’d also suggest reviewing the available documentation and endpoints before reporting items as gaps, as the required information may already be accessible through the existing API design.
Has your team heard of SQL Joins, works wonders in pulling additional data from the database.
In the List Orders endpoint you get the Contact details back, so what is the difference between Orders and Subscriptions?
You cannot have one rule in one endpoint, another rule in another endpoint.
REST v2 has now becoming an inconsistent mess.
So you are deliberately encouraging net traffic? It’s replies like this that make me wonder what ya’ll are attempting to build.