When it comes to enterprise mobile device buyback and recycling, making the process of asset disposition by the thousands at a time from many locations efficient, transparent, and hands off for the customer is key. Below are some of the API methods Mobile reCell provides for software integration. These features described for the below API's are also available in the customer portal available to Mobile reCell customers to carry out these methods or view any of this data from the user dashboard.
Submitting a Trade-in Request, receiving shipping label
This is to be used if a single device is needed to be shipped in. Typically the users name, information, device information is known including optional fields that customers can use to reference.
The OrderID returned can be used appending a url to view and print the prepaid fedex label for that shipment.
Submitting a Trade-in Request without device or user information for any quantity of devices (simply getting a pre-paid label)
This is used when a customer needs to print a pre-paid shipping label(s) to ship devices in where they may not know the device information or there are multiple devices that will be shipped in the package.
The OrderID returned can be used appending a URL to view and print the prepaid fedex label for that shipment or there is an option to use a URL parameter that can be used to generate multiple labels under the same request.
RTR (Requests, Tracking, Reporting combined)
User/device users information (of the user that submitted the request or that the request was created for, or generated the shipping label, or of which account triggered the action of the request)
device details, (This device information is gathered from what was submitted in the request by the user until the information is available in processed reporting. If there is more than one device per a single tracking number, ModelName will display the number of devices. The contents of that shipment along with processing reporting details are then available via the tracking number )
request date, business name, customer ID, order ID, tracking number, ship status, estimated value, paid value, status date, date processed
- For details on tracking use the Tracking Details API ( explained below )
- For details on shipment contents/devices processed from a shipment including condition grade and value paid for the device use the Reporting API ( explained below ). For example, all device details, processing details, value can be pulled for a tracking number those devices belonged to.
Requests is the information submitted by a user at the time a trade-in request is made. This could be before the label is generated or used for shipment. For the integrated, automated method a request, for example, could have been made automatically for an employee, the employee received the email, but could have not yet clicked through to the label or shipped the item in. There is no tracking number created until the user has viewed the label.
Requests can be compared to Tracking (below) via TrackingNumber for the ability to compare which users have or have not shipped their devices but where suppose to. Reminders could then be sent to users who have not sent in their device, but should have. This could then be compared to Tracking and Reporting (below) to see if when the device has been shipped out, what is the shipment status, and if delivered, it may also have Reporting data available.
Tracking provides the data originally sent from FedEx for each shipment update. This also includes the name of the user associated with the shipment, tracking number, status, estimated delivery date and the tracking details, for example, at which FedEx hub, in which city the package is currently located, to the location and time of the final delivery. This also includes the information about the user and device that was submitted.
Reporting provides the post-processing information captured by data wiping software as well as the condition grade, tracking number, user information that was submitted with the original request and other details about the device itself.
Response: date/time the device was processed, carrier, make, model, IMEI/MEID, model number, color, serial number, memory size, iOS, IMEI, MEID, trackNumber (Shipment tracking number), conditionGrade, users name, email, phone, address, Employee ID, date submitted, customer ID, business name, value paid for the device, FMI (icloud locked or unlocked)
Fair Market Value
Fair Market Value is the estimated current value Mobile reCell is paying for that device at the current time for A, B, C, and D condition. These values are based on what Mobile reCell has most recently paid out for the entered device at the various conditions.
There are some mobile devices we may not have fair market pricing for. This could be because it is not a common device or the device model is too old.
Search by a keyword (example: iPhone 5 Verizon 16GB)
Response: date, sold price, device information including the condition, location of the sale, selling status, the date/time the item was posted and the date/time it was sold.
Market Insights data is the information scraped from online aftermarket retail sites that includes the price an item as sold at, filterable by keyword (model name, carrier, storage, color) and condition. All data is stored in a mobile reCell database since Oct. of 2014. We do not base our quotes or fair market values on this data, but this is a helpful set of data to use to view and compare resale trends over time for mobile devices. For example, if there is a new iPhone launch this year in September and you want to view how that launch effected the used value of the previous model last year, this could help a customer determine future mobile device refresh cycles and how long to keep a device or when to sell it for a maximum value.
We will not have data on every single device model. We choose to gather information for the most common models where this type of data is useful.
Tags: mobile device buyback, recycling, enterprise buyback, API's, automated buyback program