sendgrid-csharp
sendgrid-csharp copied to clipboard
USAGE.md - missing Recipient Search with conditions [POST] example
There is missing example in USAGE.md document to search Recipients with conditions.
string data= @"{
'conditions': [
{
'field' : 'last_name',
'value': 'test last name',
'operator': 'eq',
'and_or': ''
}]
}";
dynamic response = await sg.client.contactdb.recipients.search.post(requestBody: data);
Console.WriteLine(response.StatusCode);
Console.WriteLine(response.Body.ReadAsStringAsync().Result);
Console.WriteLine(response.Headers.ToString());
Console.ReadLine();
Thanks for the heads up @robledosm! I've added this to our backlog for a fix.
@robledosm if you add this into Use Cases during October 2017, we will send you a Hacktoberfest t-shirt :)
Hello! Maybe I am not @robledosm, but I added this example to use_cases.md. Hope that will be useful for you! P.S. It's Hacktoberfest right now! ;-)
Yes I am! Thank you!
Regards,
Santiago
[https://www.lumen21.com/Content/Images/l21-logo.png] From: kostyaHrytsyuk [mailto:[email protected]] Sent: Saturday, October 28, 2017 8:27 AM To: sendgrid/sendgrid-csharp [email protected] Cc: Santiago Robledo [email protected]; Mention [email protected] Subject: Re: [sendgrid/sendgrid-csharp] USAGE.md - missing Recipient Search with conditions [POST] example (#353)
Lumen21, Inc. made the following annotations
STOP. THINK. READ. This is an external email. Exercise extra caution when responding to it, opening attachments, and/or following links.
Hello! Maybe I am not @robledosmhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frobledosm&data=02%7C01%7Csantiago.robledo%40lumen21.com%7Ccbfecd4092f740e401ac08d51df6cfca%7Cbe4544fc960a4a77845fdef270226de8%7C0%7C0%7C636447868273125860&sdata=hppsKklbUM1goTDnUO74fcZtLuLphqH3cMeBM%2FS4oII%3D&reserved=0, but I added this example to use_cases.md. Hope that will be useful for you! P.S. It's Hacktoberfest right now! ;-)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsendgrid%2Fsendgrid-csharp%2Fissues%2F353%23issuecomment-340184195&data=02%7C01%7Csantiago.robledo%40lumen21.com%7Ccbfecd4092f740e401ac08d51df6cfca%7Cbe4544fc960a4a77845fdef270226de8%7C0%7C0%7C636447868273125860&sdata=lEMw2S97oeeOBKzJDCfQOdt%2BnFkOLAc%2B4Lr2u%2FygSzM%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMV7uza5guWtahpitc1Pm0LcBPtr_LMYks5sww-FgaJpZM4KbHWx&data=02%7C01%7Csantiago.robledo%40lumen21.com%7Ccbfecd4092f740e401ac08d51df6cfca%7Cbe4544fc960a4a77845fdef270226de8%7C0%7C0%7C636447868273125860&sdata=tyUumA4Jefy6jIy5IfmPaSXlNRufShuhyGSY9iykWeU%3D&reserved=0.
NOTICE TO RECIPIENT: This communication, and any files attached, contains confidential information that may be privileged. The information is intended only for the use of the individual(s) or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Lumen21 does not guarantee that the integrity of this communication has been maintained or that this communication is free of viruses, interceptions or interferences. Lumen21 has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own validation before opening the e-mail or attachment. Lumen21 reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Thank you. END OF NOTICE
@robledosm, @kostyaHrytsyuk,
Do either of you still want to make a PR for this one? Thanks!
With Best Regards,
Elmer
This issue has been added to our internal backlog to be prioritized. Pull requests and +1s on the issue summary will help it move up the backlog.