You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello
So i have to batch a list of members who are either new or will be updated. In the docs example i saw you'd need something like this
gibbon.batches.create(body: {
operations: [{
method: "POST",
path: "lists/#{ list_id }/members",
body: "{...}" # The JSON payload for PUT, POST, or PATCH
}, ...]})
So here the JSON payload is the same. if it's a PUT or POST (the upsert and create have the exact same body), but this would not work, because the method is 'POST' and if the member is there, it will throw a 400. But if i change that to 'PUT' then this would not go through, signaling a 405 error of method not allowed.
Is updating via batching not supported or am i missing something ?
The text was updated successfully, but these errors were encountered:
Hmm, Gibbon should support anything the MailChimp API allows. Have you asked MailChimp (or I wonder if their docs mention this) whether their API supports this via the batch API? So long as the payload is formatted properly then their API determines what to do. Gibbon is just a light weight wrapper around it with no business logic to speak of
Hello
So i have to batch a list of members who are either new or will be updated. In the docs example i saw you'd need something like this
gibbon.batches.create(body: {
operations: [{
method: "POST",
path: "lists/#{ list_id }/members",
body: "{...}" # The JSON payload for PUT, POST, or PATCH
}, ...]})
So here the JSON payload is the same. if it's a PUT or POST (the upsert and create have the exact same body), but this would not work, because the method is 'POST' and if the member is there, it will throw a 400. But if i change that to 'PUT' then this would not go through, signaling a 405 error of method not allowed.
Is updating via batching not supported or am i missing something ?
The text was updated successfully, but these errors were encountered: