Problems with custom fields and system fields using the CRM JETPACK API

Viewing 1 replies (of 1 total)
  • Jay

    (@bluejay77)

    4 years, 6 months ago

    Hi @hectoreguzmanc,

    Thank you for your continued patience. We’re working on a backlog of support requests at this time, and we generally answer in the order received.

    We don’t limit API connections in the free CRM plugin; it’s a direct connection between their app and your site.

    It’s hard to tell exactly what’s going on based on the screenshots, but the short answer is that

    a) the transactions API doesn’t support custom fields, and

    b) it seems like you’re passing other fields that aren’t supported as well (e.g. “description”).

    We have an open enhancement request for adding custom fields support for our API. I have added your request to our internal backlog.

    In terms of accepted fields and correctly formatted request, please see an example here:

    https://automattic.github.io/jetpack-crm-api-docs/#transactions

    I hope that helps! Let us know if you have any other questions.

Viewing 1 replies (of 1 total)

The topic ‘Problems with custom fields and system fields using the CRM JETPACK API’ is closed to new replies.