Discussions
Problems invoicing orders in test environment
Hello,
We are experiencing an issue where we are not able to create invoices for orders. When trying to create the invoice, a small error message pops up at the bottom right saying "Failed to create consolidated invoice." The test environment is at <https://tbrologistics.roserocket.com/>. Is there some setting or other configuration required to create an invoice?
Thank you for your time
Posted by Brennan Palmer 11 months ago
Webhooks security
Is there any way to provide some security for webhooks?
Posted by Jakub Płachecki 11 months ago
I am getting error while update muli stop order
Hello,
I am getting following error while updating multistop order:
{"error_code":"5-999","error_message":"Invalid dim type"}
Posted by SadikAli 11 months ago
Get access token: 404 not found while trying to retrieve accesstoken.
![](https://files.readme.io/868ead8-image.png)
volt is org name.
Posted by admond 11 months ago
Is there an endpoint for marking invoices as PAID via API in RR?
Is there an endpoint for marking invoices as PAID via API in RR?
Posted by Anastasia Petukhova 11 months ago
Rates for a booked order
Hi, we are using "Create Booked Order" for a customer that does not require quoting. Following that creation, we would like to get the rate that order was booked at, what would be the best way to achieve that? Thank you
Posted by null 11 months ago
Tariffs using API
Hello - I cant find any documentation about Tariffs and API? Is there any API in place to upload Tariffs/Rate tables via API?
<https://help.roserocket.com/guide-to-tariffs>
Posted by Pablo 11 months ago
Edit an order after it has been dispatched - Error 5-999
No matter what I do with "Edit an order after it has been dispatched", it's giving me this error:
{
"error_code": "5-999",
"error_message": "Field Validation Errors: \\n1. Field \<request_validator.orders_edit_after_dispatched_request.order.dim_type> (Type: string) must be a valid dim type: [ltl, ftl, cube]. \\n2. Field \<request_validator.orders_edit_after_dispatched_request.order.default_measurement_unit_id> (Type: string) must be a valid measurement unit: [inch, cm, km, mi]. \\n3. Field \<request_validator.orders_edit_after_dispatched_request.order.default_weight_unit_id> (Type: string) must be a valid weight unit: [kg, lb, t, mt]. \\n4. Field \<request_validator.orders_edit_after_dispatched_request.order.billing_option> (Type: string) must be a valid billing option: [prepaid, collect, thirdparty]. \\n"
}
After playing around with network data, I'm starting to think it's a documentation problem. "billing_option" is "billing_option_id", "dim_type" is "dim_type_id", etc. I've changed what I've noticed with no luck. Any ideas?
Posted by Mike 11 months ago
Test Data in Sandbox
Hi, is there anyway to get the live data in our sandbox? We need to see how different customers will work when using API calls based on how they are set up in live now. We don't want to have to try and set up everything item by item.
Posted by null 11 months ago
endpoint to mark order paid
Hi,
Is there an endpoint to mark an order as paid in the API documentation? I can see two endpoints for marking an order as "In transit" and "Delivered", but I cannot find one for marking it as paid.
Posted by ayoub 11 months ago