Raven Industries Slingshot API

An API Key is issued by Raven to qualified ISV partners that intend on developing solutions using Slingshot data. A corresponding Shared Secret is issued at the same time. The API Key and the Shared Secret are a matched set and uniquely identify the ISV to Raven Industries, Inc. The API Key and Shared Secret are available only after a completed and signed ISV agreement has been executed.

A Shared Secret is known only to the ISV and Raven. It is the ISV's responsibility to protect the Shared Secret.

Raven issues an Access Key to Slingshot customers via the Slingshot Portal. A Slingshot portal account is required before an ISV customer can request an Access Key. Slingshot customers must be careful in allowing a third party to have an Access Key to their information. An Access Key allows a third party user (i.e., an ISV partner) to access all of a customer’s Slingshot data, including personal information protected under various jurisdictions’ privacy laws. The third party can see the Slingshot customer’s name, geographic location, details added about the machine(s), agronomic data, and any other data a Slingshot customer inputs into Slingshot or allows a machine using Slingshot to capture. A Slingshot customer may revoke an Access Key grant at any time, and revoking an Access Key grant will revoke that third party’s right to access the customer’s data on Slingshot.

All requests to the Slingshot API Server will contain the following custom HTTP headers:

These header values, along with other key components of the request will be used to provide a signature that will verify the request. Details for generating this signature can be found later in this document.

All requests to the Slingshot API Server will be authenticated in 3 ways:

1. The API Key will be verified against the Slingshot API database.
2. The request will be validated via a HMAC SHA1 signature check of key components of the request to ensure that the request came from the owner of the API Key and that the request has not been tampered with.
3. The request will have a valid lifetime of 120 seconds to prevent replay attacks.

If any of these checks fail, the Slingshot API server will respond with a 401 Unauthorized response. Details of what check failed may be returned in the body of the response.

After a request is authenticated, an authorization check will be performed using the Access Key that is part of the request. This Access Key will be used to control how much data will be returned to the client based on the account delegation configuration on the Slingshot Portal Server. An additional authorization check will be performed at the URI level to ensure that only the allowed HTTP verbs for each URI are being sent. Failed authorization attempts will result in one of the following responses:

• 401 Unauthorized
• 403 Forbidden
• 405 Method Not Allowed

In order to prevent abuse, all calls to the API are subject to a rate limit of 30 calls per every 60 seconds.

When a client has exceeded the number of API calls available during a rate limit window, all future requests will return a HTTP 429 status code.

All requests that are subject to rate limiting include the following headers that provide information about the current rate limit and the rate-limit window.

Every request to the production Slingshot API Servers must be encrypted via SSL.

The most difficult part of building a proper request to the API is building the signature and signing it with a shared secret. In any language, a properly signed signature for the request should be generated using the following steps:

1. Combine key components of the request into a single string, using a format where each value is followed by a carriage return and line feed character. The format is below:
   {Method}\r\n{Host}\r\n{URL}\r\n{Unix Timestamp}\r\n{API Key}\r\n{Access Key}\r\n
   The keywords (in curly braces) above should be replaced with the following:

   Method	HTTP Method in ALL CAPS (e.g. GET, PUT, POST, DELETE, HEAD, OPTIONS).
   Host	Host name of server in lower case (e.g. api.ravenslingshot.com).
   URL	Absolute URI minus query string in lower case (e.g. /fieldcomputers/460/PrescriptionMaps).
   Unix Timestamp	Unix style timestamp of the request (number of seconds since midnight on Jan 1 1970).
   API Key	Slingshot API Key in the case in which it was generated.
   Access Key	Slingshot Access Key in the case in which it was generated.

2. Generate an HMAC (Hash-based Message Authentication Code) using the SHA1 algorithm from the string constructed above and a 'shared secret' key.
3. The generated HMAC should then be passed along to the Slingshot API Server as the value of the X-SS-Signature request header. When the Slingshot API Server receives the request, it will do the same using the Shared Secret that matches the API Key specified in the request. If the two HMAC signatures match, the request will be considered authentic.

Examples

A function for building the signature is shown in various languages below. You can test your implementation by making sure the function produces an output of EssUFos9uCpS1FFUFaPTE3Qucz0= when provided the following strings (all encoded as UTF8):

private static string CalculateSignature(string sharedSecret,
                                         string method,
                                         string url,
                                         string host,
                                         string apiKey,
                                         string accessKey,
                                         string timestamp)
{
    string signatureBlockTemplate = "{0}\r\n{1}\r\n{2}\r\n{3}\r\n{4}\r\n{5}\r\n";
    string blockToSign = String.Format(signatureBlockTemplate,
                                       method.ToUpperInvariant(),
                                       host.ToLowerInvariant(),
                                       url.ToLowerInvariant(),
                                       timestamp,
                                       apiKey,
                                       accessKey);

    using (HMACSHA1 hmacsha1 = new HMACSHA1())
    {
        Encoding encoder = new UTF8Encoding();
        hmacsha1.Key = Convert.FromBase64String(sharedSecret);
        byte[] hmacsig = hmacsha1.ComputeHash(encoder.GetBytes(blockToSign));
        return Convert.ToBase64String(hmacsig);
    }
}
    

private String CalculateSignature(String sharedSecret,
                                  String method,
                                  String url, String host,
                                  String apiKey,
                                  String accessKey,
                                  String timestamp) throws java.security.SignatureException
{
    private String signatureBlockTemplate = "%s\r\n%s\r\n%s\r\n%s\r\n%s\r\n%s\r\n";
    String blockToSign = String.format(signatureBlockTemplate,
                                       method.toUpperCase(Locale.US),
                                       host.toLowerCase(Locale.US),
                                       url.toLowerCase(Locale.US),
                                       timestamp,
                                       apiKey,
                                       accessKey);
    String result;

    try
    {
        // get an hmac_sha1 key from the raw key bytes
        SecretKeySpec signingKey =
            new SecretKeySpec(com.ss.sscompanion.utilities.Base64.decode(sharedSecret),
                              HMAC_SHA1_ALGORITHM);

        // get an hmac_sha1 Mac instance and initialize with the signing key
        Mac mac = Mac.getInstance(HMAC_SHA1_ALGORITHM);
        mac.init(signingKey);

        // compute the hmac on input data bytes
        byte[] rawHmac = mac.doFinal(blockToSign.getBytes());

        // base64-encode the hmac
        result = com.ss.sscompanion.utilites.Base64.encodeBytes(rawHmac);
    }
    catch (Exception e)
    {
        throw new SignatureException("Failed to generate HMAC : " + e.getMessage());
    }
    return result;
}
    

        private function calculateSignature($sharedSecret,
                                            $method,
                                            $url,
                                            $host,
                                            $apiKey,
                                            $accessKey,
                                            $timestamp)
        {
            $signatureBlock =
                sprintf("%s\r\n%s\r\n%s\r\n%s\r\n%s\r\n%s\r\n",
                    strtoupper($method),
                    $host,
                    strtolower($url),
                    $timestamp,
                    $apiKey,
                    $accessKey);

            return base64_encode(hash_hmac('sha1', $signatureBlock, base64_decode($sharedSecret, true), true));
        }
    

Result set paging is supported for some API calls. The number of results returned and the relative starting offset of the result set is controlled by the following parameters:

There are several notable differences between the current version of the Slingshot API and prior releases:

• Using the pageSize HTTP query parameter, it is now possible to retrieve a complete paged result set.
• Requests for an invalid URI return an HTTP 404 result. The prior verison of the API returned an HTTP 500 result.
• This release implements a subset of the prior API release's functionality (i.e. only the API calls documented herein have been implemented and are available for use).
• Call throttling has been implemented. Exceeding 15 API requests in any 30 second window will result in the return of an HTTP 429 result.

Response Types

The Slingshot API server has three major response types: SlingshotIndex, SlingshotResponse, and Binary Data.

SlingshotIndex

The SlingshotIndex response is used to return any list of items. The header of the XML is included below:

    
    
      4
      20
      false
      false
      0
      1
    
    

Data Description

• TotalCount - The total number of records in the list being returned.
• PageSize - The number of records returned in this request. This is controlled by the optional query string parameter pageSize.
• IsPreviousPage - A Boolean value indicating if there are any pages prior to the current page in this list.
• IsNextPage - A Boolean value indicating if there are any pages after the current page in this list.
• PageIndex - The index of the current page. The page index is zero based and has a max value of TotalPages -1. This is controlled by the optional query string parameter page.
• TotalPages - The total number of pages in this list given the TotalCount and PageSize.

The rest of the SlingshotIndex response consists of summary items of the type being asked for (Field Computers, Prescription Maps, or Job Data). These entries are represented by the following XML fragment:

    
      1449
      Job from Field
      https://api.ravenslingshot.com/{nameofitem}/1449
     Subordinate type of object
    
    

Data Description

• NameOfItem - the value of this tag will be one of: FieldComputer, PrescriptionMap, JobData, or FieldHub.
• ID - The internal ID of the item.
• Name - The name of the item given to it by a Slingshot user.
• URI - the URI that can be used to retrieve more details about the item.
• SubType - only applicable to PerscriptionMap and JobData. Contains additional information about the item. For JobData items, this will contain either 'Planter', 'Sprayer', 'Yield' or Planter/Sprayer. For PrescriptionMap items, this will contain 'Prescription Map'.

Response Types

The Slingshot API server has three major response types: SlingshotIndex, SlingshotResponse, and Binary Data.

SlingshotResponse

The SlingshotResponse response is used in two situations:

• An error response where the server returns a 4XX or 5XX HTTP response.
• The server needs more time to process a request where the server returns a 200 HTTP response.

The SlingshotResponse response is represented by the following XML:

    
      
      INVALID_REQUEST
      Could not send file to Field Computer
      
      
      
    

Data Description

• status - The overall status of the response. Values include, but are not limited to.
  • INVALID_REQUEST something in the request was incorrect. The API client should use the HTTP status code to help determine what is wrong with the request.
  • MORE_TIME_NEEDED The Slingshot API server needs more time to complete the request. The API client should consult the Retry-After HTTP header to find out how many seconds it should wait before attempting to retrieve the data again.
• errorInfo - Contains text that can be displayed to the user.
• result - When result has a value, it will contain details that can be sent to Raven support for further debugging.

When an API client requests files from the Slingshot API Server, the server will respond with the binary data of the file in the response body. The server will also indicate the suggested file name via the standard HTTP header Content-Disposition. The server will indicate the type of binary data via the standard HTTP header Content-Type.

An error response where the server returns a 503 HTTP response indicating database issues.
The response will be a string "Resources exhausted. Try again.".
This means there is some database issue and the user needs to wait for some time before making further requests.

If you prefer XML, you can set the standard http header Accept to the value 'text/xml' and the Slingshot API server will send all non-binary respones to your client in XML format. Example below shows how you can set the Accept header in your code.

C#

    HttpWebRequest httpWebRequest;
    httpWebRequest = WebRequest.Create(
        new Uri("https://api.ravenslingshot.com/FieldHubs") as HttpWebRequest;
    httpWebRequest.Accept = "text/xml";
    httpWebRequest.Method = WebRequestMethods.Http.Get;
    

Examples

Slingshot Index

Example of a simple SlingshotIndex in XML

    
        
          141
          2
          false
          true
          0
          71
          
            12345678901
            Field Hub 1
            https://api.ravenslingshot.com/FieldHubs/12345678901
          
          
            12345678902
            Field Hub 2
            https://api.ravenslingshot.com/FieldHubs/12345678902
          
        
    

Slingshot Response

Example of a Slingshot Response in XML

        
        
          INVALID_REQUEST
          Item does not exist
          
        
    

If you prefer JSON, you can set the standard http header Accept to the value 'application/json' and the Slingshot API server will send all non-binary respones to your client inJSON format. Example below shows how you can set the Accept header in your code.

C#

    HttpWebRequest httpWebRequest;
    httpWebRequest = WebRequest.Create(
    new Uri("https://api.ravenslingshot.com/FieldHubs") as HttpWebRequest;
    httpWebRequest.Accept = "application/json";
    httpWebRequest.Method = WebRequestMethods.Http.Get;
    

Examples

Slingshot Index

Example of a simple SlingshotIndex in JSON

    {
       "FieldHub" : [
        {
          "ID" : "12345678901",
          "Name" : "Field Hub 1",
          "Uri" : "https://api.ravenslingshot.com/FieldHubs/12345678901"
        },
        {
          "ID" : "12345678902",
          "Name" : "Field Hub 2",
          "Uri" : "https://api.ravenslingshot.com/FieldHubs/12345678902"
        } ],
        "TotalCount" : 141,
        "PageSize" : 2,
        "IsPreviousPage" : false,
        "IsNextPage" : true,
        "PageIndex" : 0,
        "TotalPages" : 72
    }
    

Slingshot Response

Example of a Slingshot Response in JSON

        {
            "status" : "INVALID_REQUEST",
            "errorInfo" : "Item does not exist"
        }
    

Requesting and Receiving Compressed Responses

The Slingshot API supports the compression of JSON / XML responses. If you would like to use compression, set the standard http header 'Accept-Encoding' to either 'gzip' or 'deflate' and the Slingshot API server will compress the data before sending it to your client.

Requesting Compressed Responses

The following code sample shows how to set the 'Accept-Encoding' header to ask the Slingshot API for compressed responses.

    HttpWebRequest httpWebRequest;
    httpWebRequest =
    HttpWebRequest.Create("https://api.ravenslingshot.com/FieldHubs")
    as HttpWebRequest;
    httpWebRequest.Headers.Add(HttpRequestHeader.AcceptEncoding, "gzip");
    

Reading Compressed Responses

The following code sample shows how to check for a compressed response and decompress it.

C#

    //This sample merely dumps the response to the console.
    //Chage the Decompress.CopyTo target to your preferred stream
    string contentEncoding = resp.Headers["Content-Encoding"];
    if (String.IsNullOrEmpty(contentEncoding))
    {
        Console.WriteLine(resp.Content.ReadAsString());
    }
    else
    {
        if (contentEncoding.ToUpperInvariant().Contains("GZIP"))
        {
            using (GZipStream Decompress =
                new GZipStream(resp.Content.ReadAsStream(),
                CompressionMode.Decompress))
            {
                // Copy the decompression stream
                // into the output file.
                Decompress.CopyTo(Console.OpenStandardOutput());
            }
            Console.WriteLine();
        }
        else if (contentEncoding.ToUpperInvariant().Contains("DEFLATE"))
        {
            using (DeflateStream Decompress =
                new DeflateStream(resp.Content.ReadAsStream(),
                CompressionMode.Decompress))
            {
                // Copy the decompression stream
                // into the output file.
                Decompress.CopyTo(Console.OpenStandardOutput());
            }
            Console.WriteLine();
        }
        else
        {
            Console.WriteLine("compression method {0} not supported", contentEncoding);
        }
    }
    

Php

    $curl = curl_init();//initialize curl

    curl_setopt($curl, CURLOPT_URL, "https://api.ravenslingshot.com/FieldHubs");

    curl_setopt($curl, CURLOPT_HEADER, false);//false - truncates the header from the response (if you want header set it to true)
    curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);

    //prepare header
    $header = array();
    array_push($header, 'X-SS-APIKey: '. 'yourApiKey');
    array_push($header, 'X-SS-AccessKey: '. 'yourAccessKey');
    array_push($header, 'X-SS-TimeStamp: '. 'yourTimestamp');
    array_push($header, 'X-SS-Signature: '.'yourSignature');

    //request for compressed reponse
    array_push($header, 'Accept-Encoding: gzip');
    curl_setopt($curl, CURLOPT_HTTPHEADER, $header);

    //make the call
    $curl_response = curl_exec($curl);

    //uncompress the data
    $uncompressed  = gzdecode($curl_response);

    //pretty print
    echo "
".htmlentities($uncompressed)."
";

    //close curl connection
    curl_close($curl);
    

Sprayer

Planter

Yield

Quick Overview

Most of the Field Hub related API calls will return data that is coming into the Slingshot system from the Field Hub itself. This page will help you to interpret these values.

• Field Name: Active
  • Description: Indicates whether or not the Field Hub is currently reporting into the Slingshot system.
  • Data Type: Boolean
  • Units: N/A
  • Range: true or false
  • Notes:
• Field Name: Valid
  • Description: Indicates if the Field Hub is currently reporting a valid GPS position.
  • Data Type: Boolean
  • Units: N/A
  • Range: true or false
  • Notes:
• Field Name: Lat
  • Description: Latitude
  • Data Type: decmial
  • Units: decimal degrees
  • Range: -90.0 to 90.0
  • Notes:
• Field Name: Lon
  • Description: Longitude
  • Data Type: decimal
  • Units: decimal degrees
  • Range: -180.0 to 180.0
  • Notes:
• Field Name: Alt
  • Description: Altitude
  • Data Type: 32 bit Integer
  • Units: meters relative to sea level
  • Range: -2147483648 to 2147483647
  • Notes: Treated as 32 bit integer in API, practical values will come from a much narrower range.
• Field Name: Speed
  • Description: Speed over ground
  • Data Type: byte
  • Units: kilometers per hour (kmph)
  • Range: 0 to 255
  • Notes:
• Field Name: Direction
  • Description: Course over ground
  • Data Type: 32 bit Integer
  • Units: track angle degrees
  • Range: 0 to 360
  • Notes:
• Field Name: GPSSat
  • Description: Number of satellites Field Hub is tracking.
  • Data Type: byte
  • Units: N/A
  • Range: 0 to 255
  • Notes: The upper limit is determined by number of GPS satellites actually orbiting the planet.
• Field Name: GPSDateTime
  • Description: Time Stamp as reported by the GPS in the Field Hub.
  • Data Type: DateTime
  • Units: N/A
  • Range: '1000-01-01 00:00:00' UTC to '9999-12-31 23:59:59' UTC
  • Notes: Practical values will be in recent time periods; can be null. Formatted as 'YYYY-MM-DDTHH:mm:ssZ'. This value is in UTC.
• Field Name: ID
  • Description: Unique id for this record; can be used by your program to determine if this record has already been downloaded / processed.
  • Data Type: 64 bit Integer
  • Units: N/A
  • Range: 0 to 9223372036854775807
  • Notes:
• Field Name: Event
  • Description: The event that triggered the Field Hub report
  • Data Type: String
  • Units: N/A
  • Range: "1", "2", "3", "4", "5", "16", "17", "30", "31"
  • Notes:
  1 - Digital Input 1 state change
  2 - Digital Input 2 state change
  3 - Digital Input 3 state change
  4 - Digital Input 4 state change
  5 - 5 second update
  16 - Ignition Power On
  17 - Ignition Power Off
  30 - 30 second update
  31 - 30 second upate
• Field Name: DeviceId
  • Description: This is the actual Device ID
  • Data Type: String
  • Units: N/A
  • Range: N/A
  • Notes:
• Field Name: GPSFix
  • Description: Indicates if the GPS antenna is 'fixed' onto a group of satellites.
  • Data Type: Boolean
  • Units: N/A
  • Range: true or false Notes:
• Field Name: RSSI
  • Description: Receive Signal Strength Indicator in dBm
  • Data Type: Signed Byte
  • Units: dBm
  • Range: -103.0 to -85.0
  • Notes:
    RSSI >= -85.0 → 5 bars
    -85.0 > RSSI >= -90.0 → 4 bars
    -90.0 > RSSI >= -95.0 → 3 bars
    -95.0 > RSSI >= -100.0 → 2 bars
    -100.0 > RSSI >= -103.0 → 1 bar
    -103.0 > RSSI → 0 bar
• Field Name: Ignition
  • Description: Ignition State
  • Data Type: Boolean
  • Units: N/A
  • Range: true or false
  • Notes:
• Field Name: DigitalInput1
  • Description: State of Digital Input 1 on the back of the Field Hub
  • Data Type: Boolean
  • Units: N/A
  • Range: true or false
  • Notes: Interpretation is application specific
• Field Name: DigitalInput2
  • Description: State of Digital Input 2 on the back of the Field Hub
  • Data Type: Boolean
  • Units: N/A
  • Range: true or false
  • Notes: Interpretation is application specific
• Field Name: DigitalInput3
  • Description: State of Digital Input 3 on the back of the Field Hub
  • Data Type: Boolean
  • Units: N/A
  • Range: true or false
  • Notes: Interpretation is application specific
• Field Name: DigitalInput4
  • Description: State of Digital Input 4 on the back of the Field Hub
  • Data Type: Boolean
  • Units: N/A
  • Range: true or false
  • Notes: Interpretation is application specific
• Field Name: AnalogInput1
  • Description: Value received on Analog Input 1 on the back of the Field Hub
  • Data Type: Double
  • Units: N/A
  • Range: 0.0 to 15.0
  • Notes: Interpretation is application specific
• Field Name: AnalogInput2
  • Description: Value received on Analog Input 2 on the back of the Field Hub
  • Data Type: Double
  • Units: N/A
  • Range: 0.0 to 15.0
  • Notes: Interpretation is application specific
• Field Name: AnalogInput3
  • Description: Value received on Analog Input 3 on the back of the Field Hub
  • Data Type: Double
  • Units: N/A
  • Range: 0.0 to 15.0
  • Notes: Interpretation is application specific
• Field Name: AnalogInput4
  • Description: Value received on Analog Input 4 on the back of the Field Hub
  • Data Type: Double
  • Units: N/A
  • Range: 0.0 to 15.0
  • Notes: Interpretation is application specific
• Field Name: BatteryVoltage
  • Description: Value of the voltage as measured on the Field Hub power input connection
  • Data Type: Double
  • Units: volts
  • Range: 0.0 to 30.0
  • Notes:
• Field Name: DigitalOutput1
  • Description: State of Digital Output 1 on the back of the Field Hub
  • Data Type: Boolean
  • Units: N/A
  • Range: true or false
  • Notes: Interpretation is application specific
• Field Name: DigitalOutput2
  • Description: State of Digital Output 2 on the back of the Field Hub
  • Data Type: Boolean
  • Units: N/A
  • Range: true or false
  • Notes: Interpretation is application specific
• Field Name: DigitalOutput3
  • Description: State of Digital Output 3 on the back of the Field Hub
  • Data Type: Boolean
  • Units: N/A
  • Range: true or false
  • Notes: Interpretation is application specific
• Field Name: ServerDateTime
  • Description: The UTC Date and Time of when the record was written to the Slingshot system.
  • Data Type: DateTime
  • Units: N/A
  • Range: '1970-01-01 00:00:01' UTC to '2038-01-19 03:14:07' UTC
  • Notes: Practical values will be in recent time periods; can be null. Formatted as 'YYYY-MM-DDTHH:mm:ssZ'. This value is in UTC.
• Field Name: Odometer
  • Description: Distance the Field Hub has traveled in hectometers.
  • Data Type: Unsigned 32 bit Integer
  • Units: hectometers
  • Range: 0 to 4294967295
  • Notes: This is calculated from the distance the Field Hub has traveled between fixed GPS locations.
• Field Name: Service
  • Description: The name of the service the Field Hub is currently using.
  • Data Type: String
  • Units: N/A
  • Range: N/A
  • Notes: This value comes directly from the Field Hub. Some values we've seen are: "", "NONE", "1xRTT", "EVDO", "EVDO.A", "GPRS", "EDGE", "UMTS", and "HSPA".
• Field Name: Carrier
  • Description: The name of the wireless carrier the Field Hub is currently using.
  • Data Type: String
  • Units: N/A
  • Range: N/A
  • Notes: This value comes directly from the Field Hub. Some values we've seen are: "AT&T", "Bell", and "Verizon".
• Field Name: Roam
  • Description: An indicator that the Field Hub is in 'Roaming' mode, as determined by the Field Hub.
  • Data Type: String
  • Units: N/A
  • Range: N/A
  • Notes:

"" - Roaming status cannot be determined. "00" - Field Hub is not roaming. Any other value - Field Hub is roaming.

Getting the GPS Location of a Field Computer consists of 2 steps:

1. Determining the ID of the Field Computer to be located
2. Asking the Slingshot API Server for the GPS Location(s) of the chosen Field Computer

    2
    20
    false
    false
    0
    1
    
        2058
        VPRO4 T380
        https://api.ravenslingshot.com/FieldComputers/2058
    
    
        2558
        E-Pro II B2
        https://api.ravenslingshot.com/FieldComputers/2558
    

    

    1
    20
    false
    false
    0
    1
    
        253006
        1092
        Field Computer
        0.00000000
        0.00000000
        0
        0
        0
        2010-10-05T18:03:20Z
    

    

    1990
    20
    false
    true
    0
    100
    
        253006
        1092
        Field Computer
        0.00000000
        0.00000000
        0
        0
        0
        2010-10-05T18:03:20Z
    
    
        253005
        1092
        Field Computer
        0.00000000
        0.00000000
        0
        0
        0
        2010-10-05T17:58:10Z
    

    

Uploading a Rx Map and sending it to a Field Computer consists of 3 steps:

1. Determining the ID of the Field Computer that should receive the Rx Map
2. Uploading the Rx Map to the Slingshot API Server (this will provide contains the URI of the newly POSTed file)
3. Directing the Slingshot API Server to send the Rx Map to the chosen Field Computer

    2
    20
    false
    false
    0
    1
    
        2058
        VPRO4 T380
        https://api.ravenslingshot.com/FieldComputers/2058
    
    
        2558
        E-Pro II B2
        https://api.ravenslingshot.com/FieldComputers/2558
    

    

    $method = "POST";
    //initialize curl
    $curl = curl_init();

    curl_setopt($curl, CURLOPT_URL, "https://api.ravenslingshot.com/PrescriptionMaps");
    curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);

    //create header for authentication
    $header = getHeaders($method, "api.ravenslingshot.com", strtolower ("/PrescriptionMaps"));
    array_push($header, 'Accept: application/xml');
    curl_setopt($curl, CURLOPT_HTTPHEADER, $header);

    //handle file upload
    if($method == "POST")
    {
        //it is a post
        curl_setopt($curl, CURLOPT_POST, true);
        $filePath = 'C:\PrescriptionMap.zip'; //file location
        //array for file information
        $postData = array(
                "FileType" => "RX",//or AGX
                "FileName" => "@".realpath($filePath)
                );
        //attach filetype and filename
        curl_setopt($curl, CURLOPT_POSTFIELDS, $postData);
    }
    //handle file ends here

    //make the call
    $curl_response = curl_exec($curl);
    //pretty print
    echo "
".htmlentities($curl_response)."
";
    curl_close($curl);