Unicode C++
Unicode C++
PayPal - Cancel Sent Invoice
See more PayPal Examples
Cancels a sent invoice, by ID, and, optionally, sends a notification about the cancellation to the payer, merchant, and Cc: emails.Note: This example requires Chilkat v9.5.0.65 or greater.
Chilkat Unicode C++ Downloads
#include <CkJsonObjectW.h>
#include <CkStringBuilderW.h>
#include <CkRestW.h>
void ChilkatSample(void)
{
bool success = false;
// Note: Requires Chilkat v9.5.0.65 or greater.
// This requires the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.
// Load our previously obtained access token. (see PayPal OAuth2 Access Token)
CkJsonObjectW jsonToken;
jsonToken.LoadFile(L"qa_data/tokens/paypal.json");
// Build the Authorization request header field value.
CkStringBuilderW sbAuth;
// token_type should be "Bearer"
sbAuth.Append(jsonToken.stringOf(L"token_type"));
sbAuth.Append(L" ");
sbAuth.Append(jsonToken.stringOf(L"access_token"));
// Make the initial connection.
// A single REST object, once connected, can be used for many PayPal REST API calls.
// The auto-reconnect indicates that if the already-established HTTPS connection is closed,
// then it will be automatically re-established as needed.
CkRestW rest;
bool bAutoReconnect = true;
success = rest.Connect(L"api.sandbox.paypal.com",443,true,bAutoReconnect);
if (success != true) {
wprintf(L"%s\n",rest.lastErrorText());
return;
}
// ----------------------------------------------------------------------------------------------
// The code above this comment could be placed inside a function/subroutine within the application
// because the connection does not need to be made for every request. Once the connection is made
// the app may send many requests..
// ----------------------------------------------------------------------------------------------
// Build the JSON request body containing the reminder information:
CkJsonObjectW json;
json.put_EmitCompact(false);
json.UpdateString(L"subject",L"Past due");
json.UpdateString(L"note",L"Canceling invoice");
json.UpdateBool(L"send_to_merchant",true);
json.UpdateBool(L"send_to_payer",true);
wprintf(L"%s\n",json.emit());
// The JSON created by the above code:
// {
// "subject": "Past due",
// "note": "Canceling invoice",
// "send_to_merchant": true,
// "send_to_payer": true
// }
// Build a path using a previously-sent invoice ID.
CkStringBuilderW sbPath;
sbPath.Append(L"/v1/invoicing/invoices/invoice_id/cancel");
int numReplacements = sbPath.Replace(L"invoice_id",L"INV2-XPWZ-NUTQ-LNWB-P8NC");
json.put_EmitCompact(true);
CkStringBuilderW sbRequestBody;
CkStringBuilderW sbResponseBody;
rest.AddHeader(L"Content-Type",L"application/json");
rest.AddHeader(L"Authorization",sbAuth.getAsString());
json.EmitSb(sbRequestBody);
success = rest.FullRequestSb(L"POST",sbPath.getAsString(),sbRequestBody,sbResponseBody);
if (success != true) {
wprintf(L"%s\n",rest.lastErrorText());
return;
}
wprintf(L"Response Status Code = %d\n",rest.get_ResponseStatusCode());
// In our testing, we received a 204 response, which is a success HTTP response code, but
// differs from the PayPal REST API reference documentation, which states that a 202 response
// is expected. I suspect an error in the PayPal documentation, or in the PayPal responder.
// Check for either 202 or 204..
// Did we get a 202 accepted response?
if ((rest.get_ResponseStatusCode() != 202) && (rest.get_ResponseStatusCode() != 204)) {
wprintf(L"%s\n",sbResponseBody.getAsString());
wprintf(L"Failed.\n");
return;
}
// The 202/204 response should be empty. (Again, our experience differs from the online PayPal documentation..)
wprintf(L"Success.\n");
}