Hi @Mark_Ginat,
Thanks so much for the detailed feedback and for clearly outlining these gaps. I really appreciate you taking the time to provide all the specifics; it makes it much easier for us to understand the issues and discuss potential solutions.
Gap #1: No REST API endpoint to update payment method expiration date
In v2, there is no direct endpoint to edit an existing payment method. Card data is managed by the payment processors (e.g., Stripe, Rainforest). The supported approach is to delete the old payment method and create a new one with the updated expiration.
For guidance on how payment methods are handled in v2, please see the documentation:
Keap Payments API Integration Configuration
This approach is intentional and reflects the way v2 is designed: cards are no longer treated as entities owned by our system, and updates like expiration changes are handled through the payment processors’ components.
Gap #2: No REST API endpoint to query Invoice table by contact
In v2, orders and invoices are handled in a more unified way, so an order essentially represents its invoice. You can use the GET /v2/orders endpoint and filter by contact_id. Can you confirm if this meets your need?
Gap #3: No REST API endpoint to query Payment table
Thanks for reporting this, I will bring it up internally.
Gap #4: CreditCard table ID ≠ REST payment_method_id (no mapping provided)
- You actually reported this one here, and I’ve already flagged it internally.
Gap #5: No REST API endpoint to update Order (Job) custom fields
- I will report it, thanks for bringing it up.