PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Campaign Monitor API for client is being rejected

  1. Is there a way to by-pass the main campaign monitor api and use the client specific api? Or is the main api the only one that is accepted? I'd rather not have the different people accessing the site see all the other people I have on Campaign Monitor.

    Posted 8 years ago on Tuesday July 27, 2010 | Permalink
  2. Client API keys don't appear to work with Campaign Monitor the way our add-on is implemented. When the add-on was developed they had not implemented client API keys, only parent API keys.

    Until we look into how we can change our add-on to support client API keys, if possible, you can use role management to limit the users access to this area of Gravity Forms so they can't access it.

    Posted 8 years ago on Tuesday July 27, 2010 | Permalink
  3. Thanks. I was hoping I didn't have to do that. It would be a great feature to add down the road.

    Posted 8 years ago on Tuesday July 27, 2010 | Permalink
  4. Andytsai
    Member

    Please notify me when client api is supported.
    It's the main reason why I bought the developer license, yet it's not supported yet.

    Posted 8 years ago on Friday November 5, 2010 | Permalink
  5. @Andytsai - join our mailing list if you're interested in getting timely updates. The form is on the bottom of the site at http://www.gravityforms.com.

    Posted 8 years ago on Friday November 5, 2010 | Permalink
  6. Ooohhh men, these sucks, I just built my "coming soon" page using Gravity Forms and Campaign Monitor Addon, now I know why it didn't work.

    http://optimiza.mx/

    Posted 8 years ago on Thursday December 9, 2010 | Permalink
  7. @miguel We are going to take a look at this today and see if we can get this resolved soon. We have to see if the PHP SDK we are using supports it, if not we may need to make some updates. But we are going to look into this today.

    Please note that everything works, it just doesn't work with the client API key. You have to put the main account API key in and then when setting up your integration you select the client, and then select a list from the lists associated with that client.

    So it's fully usable as long as you have the parent API key. Campaign Monitor didn't support client API keys when we developed the add-on.

    Posted 8 years ago on Thursday December 9, 2010 | Permalink
  8. @Carl Hancock thanks for the reply. I did the correct setup since the beginning because the API client didn't worked, then I use the main API and it was accepted by the plugin. Everything was setup correctly, it just not sending the fields (name) (email) to campaign monitor.

    Anyways, I'll wait until is fully working, I will use it on my website too, not only the coming soon page.

    Thanks!

    Posted 8 years ago on Thursday December 9, 2010 | Permalink
  9. I still can't use the Add-on as it is because using the Master API Key is essentially giving the client full access to the master account (which is obviously not desired). I just tested the Client API Key against the latest version with no joy.

    I've only just now found out how to get the "Client API Key" (https://api.createsend.com/api/v3/apikey.json?siteurl=yournamehere.createsend.com) instead of the "API Client ID"... (unfortunate naming).

    Campaign Monitor tech support: "If that route is called with the client's username/password, it will return an enduring ApiKey that provides access to that client's resources alone. Call it once and you can save it, knowing that it will work again. With that ApiKey you can still create and send campaigns, lists, segments, import subscribers; the works. The GravityForms plugin (and others) should just work."

    Also, "this client-specific ApiKey is a replacement for the designer ApiKey, not the clientID. You will still need the normal clientID when doing things like creating lists."

    Any update on your end in the works for this? We've been dying to streamline our workflow...

    Thanks,
    Ken Newman,
    employee at adcSTUDIO

    Posted 6 years ago on Wednesday April 11, 2012 | Permalink