Entry Summary
Strix web service integration documentation
Overview
CBP entry summary filing (CATAIR). Header, invoices, line items, tariffs, and PGA data.
entry is the root element of the document. The sub-elements of the entry tag must appear in the order specified below.
entryMessage structure
Available operations
SOAP 1.1 (RPC/literal)uploadEntryParameters: username, password, entryXml
Returns: XML response (string)
amendEntryParameters: username, password, entryXml
Returns: XML response (string)
queryEntryStatusParameters: username, password, entryNumber, externalReferenceNumber
Returns: XML response (string)
queryType86EntryStatusParameters: username, password, queryTimeRange
Returns: XML response (string)
updateBolParameters: username, password, bolUpdateXml
Returns: XML response (string)
deleteType86EntryByMawbParameters: username, password, mawbPrefix, mawbNumber
Returns: XML response (string)
deleteEntryParameters: username, password, entryNumber, masterBill, entryStatusFilter, cargoReleaseStatusFilter, entrySummaryDelete, cargoReleaseDelete, releaseReason, multipleCargoDisposition, disSubmissionMade, replacementNo
Returns: XML response (string)
Example request
Example responses
<accepted>
<entry-no>ABC-0000001-1</entry-no>
</accepted>ENTRY XSD Fields
entry-noThe purpose of the <entry-no> tag is to tell Strix how the entry-no for this entry should be created. The <entry-no> tag can have 2 possible values. The first is <user-specified>. If this is included, then the <user-specified> element must contain 2 elements, <filer-code> and <entry-no>, respecitvely. The value for the <entry-no> element must be a 7 or 8 digit number. A valid <user-specified> group would be: <user-specified> <filer-code>ABC</filer-code> <entry-no>1234567</entry-no> </user-specified>. An entry number must be 7 digits, except in rare cases where you need an 8-digit number to amend an entry. If amending an entry with a different check digit than the one currently set in your account (Account - Preferences - Entry Number), the 8-digit number will include the check digit of the entry you're amending as the first digit. For example, if your current check digit is 2 but you're amending an entry with a check digit of 1, you would use: <user-specified> <filer-code>ABC</filer-code> <entry-no>12345678</entry-no> </user-specified> In this case, the check digit is 1. The other option is <system-generated>. This means that Strix will create the entry number for this entry. This should be included as a simple empty tag, <system-generated />
precalculatedThis is an optional tag. If present, this informs Strix that duties and fees have already been calculated, and Strix will not calculate duties and fees for the entry.
remove-ddpThis is an optional tag. If present, Strix will perform a calculation to remove the DDP from the entered value of each line
transmitThe <transmit /> tag is optional. If included, Strix will automatically transmit the entry summary to customs once the upload of this entry is complete.
transmit-3461The <transmit-3461/> tag is optional. If included, Strix will automatically transmit the cargo release to customs once the upload of this entry is complete. If the <transmit> is included, this tag is generally not necessary.
via-aceThe <via-ace/> tag is optional. If included, the entry will be sent via ACE. Additional ACE data fields should be included in the XML. This tag is deprecated. All entries will be set via ACE.
external-reference-numberThis tag should include a reference number or unique ID from your system that servers as a unique identifier for all transmissions sent back to your system. Strix will include an <external-reference-number> tag with this value unchanged in cargo release updates or entry summary updates, etc. sent back to your system.
assign-toThis is the username of the user who this entry should be assigned to. This tag is optional. If this tag is omitted, the entry will be assigned to the user whose username and password is submitted as the security credentials for the uploadEntry/amendEntry operations on this web service
auto-apply-remediesThis tag will auto apply the found trade remedies for the lines with only a single Tariff. This allows users to overwrite the auto apply functionality by explicitly declaring the trade remedies to the line.
apply-exemptionsThis tag will used with the auto apply remedy tag, will replace remedies with exemptions that are marked to apply.
single-smelt-remedyThis tag requires the 'auto-apply-remedies' tag and will only apply the Aluminum trade remedy to the line if either Aluminum or both Aluminum and Steel trade remedies applies.
default-aluminum-countryThis tag is used to default the Aluminum Smelt Country Information for all Aluminum tariffs. If this tag is left empty but included in the request, the system will use the Country of Origin as the Aluminum Smelt Country. If a country is entered in the tag, the system will set the Aluminum Tariff information to said country. Valid values are the 2 digit Country Code, empty to default to country of origin, or UN if country of smelt is not known.
default-steel-countryThis tag is used to default the Steel Smelt Country Information for all Steel tariffs. If this tag is left empty but included in the request, the system will use the Country of Origin as the Steel Smelt Country. If a country is entered in the tag, the system will set the Steel Tariff information to said country. Valid values are "", "The 2 digit Country Code", or "UKN" if country of smelt is not known.
default-copper-countryThis tag is used to default the Copper Smelt Country Information for all Copper tariffs. If this tag is left empty but included in the request, the system will use the Country of Origin as the Copper Smelt Country. If a country is entered in the tag, the system will set the Copper Tariff information to said country. Valid values are "", "The 2 digit Country Code", or "UKN" if country of smelt is not known.
disclaim-cotton-feeIf this tag is present, anywhere cotton fee could apply in the entry, it will be disclaimed.
consolidated-entriesNo description provided in this schema.
containersNote: The <containers> tag can have two types of child tags, <container-number> or <container>. The <container> tag allows you to include more information, such as the seal number (see entry:containerType). The <container-number> tag only allows you to upload the container number.
ace-cargo-release-partiesThis should be included if the entry is sent via ACE and the <certify-cargo-release-via-ace/> tag is included. The buying party and selling party are required. All other parties are optional. For entry type 86 only the seller and consignee are required.
email-notificationsThis is for the Email Notification Preferences on the Entry Main Menu