Library . Nexmo . Search . SearchMessagesByRecipientAndDate

Searches sent messages by Date and Recipient. Note that a sent message won't be immediately available for searching.

Input
• APIKey Your API Key provided to you by Nexmo.
• APISecret Your API Secret provided to you by Nexmo.
• Date Date message was sent in the form of YYYY-MM-DD (UTC). (e.g. 2013-07-01)
• To The recipient's phone number. (e.g. 123456780)
Optional Input
• ResponseFormat The format that the response should be in. Valid values are "json" (the default) and "xml".
Log In To Run
• Output
  Actuator Trigger Condition

  If{"Response":{"type":"","description":"The response from Nexmo. Corresponds to the ResponseFormat input. Defaults to json. Note that if no matches are found for the specified Date and To, the Response will contain an error-code \"-2\"."},"Success":{"type":"boolean"}}ResponseSuccess then write

  High Low

  to at

  • Response The response from Nexmo. Corresponds to the ResponseFormat input. Defaults to json. Note that if no matches are found for the specified Date and To, the Response will contain an error-code "-2".
• CHOREO CLASS

  • /*
    TembooTask class placeholder
    */

• iOS HEADER

  • /*
    TembooTask header placeholder
    */

• • Simple
  Enhanced
  Add a sensor via the virtual pin board above to generate code for sensor data graphs.
  Compiled
  Add a sensor or actuator via the virtual pin board above to generate compiled code for sensor data graphs and remote actuator control.
  Device Configure Changed

  Since you've changed your device configuration, you'll need to tell us about this new device.

  Update Device
  1. Add a sensor or actuator to your device.
  2. Register your board and download your code.

  Download
  • Download editable code
  • Commit to GitHub
  • Send to CCS Cloud

  OK! Let's set up your device

  This feature is in experimental mode - pricing coming soon.

  Device Name *

  Device ID

  Description

  Location *

  Use lat/long

  Sensor Data
  Frequency *

  Pro Tip!

  Power consumption will increase if you choose a higher frequency.

  Every 30 seconds Every minute Every 5 minutes Every 30 minutes Every hour Every day Custom interval

  Safeguard data

  what's this?

  If connectivity is lost, up to 2MB of data will be stored locally on your device, and updated when connectivity is restored.

  + new tag

  Save
  Commit your generated code
  and collaborate with others.

  Send your code straight to a GitHub repository.

  Collaborating on GitHub?

  Your code will be visible by others in your repos. Keep credentials private by saving a Profile or commit code with Placeholder inputs.

  Choose a GitHub Repository

  Name:

  The following files will be added to this repo:

  * Don't worry! Your credentials and any inputs that aren't saved in a Profile will not be included.

  Success!

  Visit the link below to view, modify, and share code.

  Cancel Commit code to GitHub Use Placeholders Save a Profile Commit Close
  Send code to CCS Cloud.

  You'll be able to edit and share your code from TI's CCS Cloud IDE.

  Name your application

  Names can only contain letters, numbers, hyphens, and underscores.

  The following will be sent to CCS Cloud:

  TembooMain.c

  TembooAccount.h

  instructions.txt

  + 9 others

  Success!

  Visit the link below to view, modify, and share code.

  https://dev.ti.com/ide/

  Cancel Send to CCS Cloud Send Close
  Code

  • // Instantiate the Choreo, using a previously instantiated TembooSession object, eg:
    // TembooSession session = new TembooSession("accountName", "myFirstApp", "abc123xxxxxxxxxxxxxx");
    
    SearchMessagesByRecipientAndDate searchMessagesByRecipientAndDateChoreo = new SearchMessagesByRecipientAndDate(session);
    
    // Get an InputSet object for the choreo
    SearchMessagesByRecipientAndDateInputSet searchMessagesByRecipientAndDateInputs = searchMessagesByRecipientAndDateChoreo.newInputSet();
    
    // Set inputs
    
    // Execute Choreo
    SearchMessagesByRecipientAndDateResultSet searchMessagesByRecipientAndDateResults = searchMessagesByRecipientAndDateChoreo.execute(searchMessagesByRecipientAndDateInputs);

• Header File

  • /* 
    A header file containing your Temboo account information will appear here once you've
    configured your device above.
    */

• Proxy Code

  • /*
    Please log in to generate proxy server code for use with the JavaScript SDK.
    */

• Notes

  • This Choreo searches sent messages by Date and Recipient. Note that a sent message won't be immediately available for searching. The documentation for this Nexmo resource can be found here.

    Here's an example list of acceptable inputs:

    APIKey: da9bb2ab
    APISecret: 14f9b38c
    Date: 2011-05-11
    To: 3472804545
    

    The following is a sample of an XML formatted response returned by this Choreo:

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <messages>
        <count>count</count>
        <items>
            <message>
                <type>type</type>
                <message-id>id</message-id>
                <account-id>account</account-id>
                <network>network</network>
                <from>from</from>
                <to>to</to>
                <body>body</body>
                <price>price</price>
                <date-received>date</date-received>
                <date-closed>date</date-closed>
                <final-status>final-status</final-status>
                <latency>latency</latency>
                <status>status</status>
            </message>
        </items>
        <error-code>error</error-code>
        <error-code-label>label</error-code-label>
    </messages>

    The following is a sample of a JSON formatted response returned by this Choreo:

    {
        "count": count,
        "items": [
            {
                "message-id": "id",
                "account-id": "account",
                "network": "network",
                "from": "from",
                "to": "to",
                "body": "text",
                "price": "price",
                "date-received": "YYYY-MM-DD HH:MM:SS",
                "final-status": "status",
                "date-closed": "YYYY-MM-DD HH:MM:SS",
                "latency": "latency in ms",
                "type": "type"
            }
        ]
    }