ENUM
WebhookEventType
A webhook event type
link Webhook Events
All events are sent via webhook. You define a single HTTP endpoint that can receive POST messages with a JSON body, and we send events to that endpoint in real time. Some examples are below:
A single payload can contain multiple events, and each event includes a JSON body field specific to that event type. A full list of event types can be found here.
You will choose 1 test endpoint and 1 production endpoint. We will send your test/production API key in the x-api-key header which you can use to verify the sender.
During testing, you can use the triggerEvent mutation to send webhook events to the test endpoint. We have found ngrok to be a great way to setup a test endpoint that tunnels to your localhost server.
If the webhook fails to send, we will retry 1 second later, and 2 seconds after that. If none of these 3 attempts work, we will send an email with the event and error to an inbox you specify.
importers_activated |
An Importer has been activated for use |
---|---|
shipments_billMatch |
An ISF has received a bill match with Customs |
shipments_inquireDoc |
An additional document is required for Customs entry |
shipments_customsHold |
A Customs hold has occurred on a Shipment |
shipments_customsRelease |
A Shipment has been released by Customs |
invoices_invoiced |
A new Invoice has been generated |
A single payload can contain multiple events, and each event includes a JSON body field specific to that event type. A full list of event types can be found here.
You will choose 1 test endpoint and 1 production endpoint. We will send your test/production API key in the x-api-key header which you can use to verify the sender.
During testing, you can use the triggerEvent mutation to send webhook events to the test endpoint. We have found ngrok to be a great way to setup a test endpoint that tunnels to your localhost server.
If the webhook fails to send, we will retry 1 second later, and 2 seconds after that. If none of these 3 attempts work, we will send an email with the event and error to an inbox you specify.
link GraphQL Schema definition
- enum WebhookEventType {
- # INLT received a response from AMS
- # An Importer has signed a document (ImporterEventBody)
- # INLT has a question about an Importer's Power of Attorney which is preventing
- # their activation. The Importer's status will change to PENDING_INQUIRY.
- # (ImporterEventBody)
- # An Importer's Power of Attorney has been rejected and a new link has been
- # generated for an officer to sign. The Importer's status will revert to one of
- # the PENDING_* statuses based on the document that was rejected.
- # (ImporterEventBody)
- # INLT has activated an importer for use (ImporterEventBody)
- # Customs has approved an importer for Periodic Monthly Statements
- # (ImporterEventBody)
- # INLT has has a question about one of the documents uploaded to the shipment
- # (ShipmentEventBody)
- # INLT has rejected one of the documents uploaded to the shipment
- # (ShipmentEventBody)
- # Customs has accepted an Importer Security Filing (10+2) (ShipmentEventBody)
- # Customs has rejected an Importer Security Filing (10+2) (ShipmentEventBody)
- # Customs has accepted an Entry, includes 7501 in PDF format (ShipmentEventBody)
- # A mock-7501 in PDF format for the importer to confirm before submitting an Entry
- # to Customs (ShipmentEventBody)
- # Customs has released a shipment, includes 7501 and ACE Cargo Release in PDF
- # format (ShipmentEventBody)
- # Customs has placed a shipment on a temporary hold (ShipmentEventBody)
- # Customs has held a shipment for an intensive exam (ShipmentEventBody)
- # A Partner Government Agency (FDA, EPA...) has released a shipment
- # (ShipmentEventBody)
- # A Partner Government Agency (FDA, EPA...) has held a shipment
- # (ShipmentEventBody)
- # A shipment has been canceled (ShipmentEventBody)
- # An invoice from INLT in PDF and JSON format (InvoiceEventBody)
- # An invoice has been voided (InvoiceEventBody)
- }