Inferences
Retrieve shipping labels
Once you have scan the shipping label, you can query for them in the API. If you have the developer or owner role, you're able to also view the scans on your dashboard at https://cloud.packagex.io/inferences/shipping-labels.
Retrieve Scan
Get a single scan using its id
.
List Shipping-Labels
Example
When you want to retrieve multiple shipping-labels, your data
property on the result will always be an array
even if you don't have any shipping-labels. The shipping-labels are returned in descending order, meaning the latest scan that was created will be first.
Pagination
If the has_more
property on the pagination object is set to true, you know there are more scans in the database that have not been returned to you. The pagination object also has a page
property indicating your current offset and a limit property. The total_count property in pagination returns the the total number of scans in the database.
By default the page
is set to 1
and the limit
is 10
.
If we want to query for scans 11 - 20, we would request page 2 with a query parameter.
Filter
- Location Filtering
- Scans with a
location_id
property can be filtered by location.
- Provider filtering:
- You can now filter by
provider_name
.
- Service level filtering:
- Filtering options include
service_level_name
.
Similarly we can also filter on date and package status.
Status
Date
Search
There are times when filtering is not enough and you want to find a specific inference by some other attribute. In this case, you can do a fuzzy, typo-tolerant search of every inference in the database. Below are the properties that are supported by our full text search.
Searchable Properties
order_number
tracking_number
rma_number
reference_number
invoice_number
purchase_order
barcode_values
recipient.name
recipient.email
recipient.business
sender.name
sender.email
sender.business
To search, simply provide a string to search by using the search
query param. The results will be order by the most relevant first.
If you want to highlight matching search results for a frontend, we provide a special property for search-returned inference objects called _search
which will have the matched text surrounded with <mark>
handles.
Ordering Search Results
By default, search results are ordered by relevance. However, if you include an order_by
parameter along with your search query, the results will be ordered by the specified property instead of by relevance.
Relevance Score
Relevance scores are included in the search results by default. Note that this could add up to 10ms of extra time to the request.