Please see API documentation for implementation details. Here list the details required for updateRFC mutation.
query:
mutation UpdateRFC($input: RFCInput) { updateRFC(input: $input) }
variables:
- Note all time is in UTC time ISO format 2025-06-11T03:52:19.208Z
{
"input": {
"bookingUuid": "a9254908-627f-4d93-b993-92378c6546af",
"rfcInput": {
"rfcDate": "2025-06-11T03:52:19.208Z",
"estimatedRfcDate": "2025-06-11T03:52:19.208Z",
"dropoffPoint": "f7b25e30-6b73-4f81-8486-6db5e57583a5",
"lastPortStorageDatetime": "2025-06-13T03:52:19.208Z",
"rfcRemarks": "testing for life",
"collectionHours": "24hours"
},
"_ext": {
"rfcInput.dropoffPoint": "myExternalDropOffPoint"
}
}
}For external mapping, note the _ext value in the bottom. All fields entered into this will bypass validation and the mapping will be done by the operations team in ShipX. If the field is required, and not passed in the body or _ext field, the validation will still fail. If both fields are pass, the fields in the ext mapping will always take priority.