ssc
ssc copied to clipboard
freightapis
Holds artifacts created by the SSC
- Proposal to support this as a web hook event by Carrier systems - Scheduling system can ping parodically ping about location updates and other optional attributes such as temperature...
- Proposal to support this as a web hook event by TMS system such as Buyer TMS or a Supplier TMS, depending on who manages freight - Whenever carrier is...
From Convoy internal review: > Can/should we attempt to align our webhook implementation with folks in the industry trying to make them easier, e.g. Svix, Hook0, etc?
Wanted to start a thread on defining and communicating compliance so we're all aligned. Compliance: - If TMS removed/renamed any parts of the SSC spec, they are not in compliance...
1. When I provide a `primaryReferenceNumber` and a `locationIdentifier`, I should receive a successful response with the response defined in the spec.
A status indicating the TMS's ability to use the webhook that the client registered at the TMS might be helpful if one was available in the spec. The client could...
We've discussed at detail scenarios where an API implementer might add _additional_ required fields to their requests/responses that aren't part of the official spec, but we haven't discussed scenarios where...
https://github.com/freightapis/ssc/discussions/12 Need to discuss about adding comments to Fetch Available Appointments.
#12 Use case 1: In situations where the facility is open and is already at capacity therefore no appointments are available, many shippers want the ability to communicate to carriers...
Use Case: As a carrier, I can only leverage the API for Shipping Company A's appointments if they are enabled with the Appointment Scheduling Tool. In this example, it would...