The Shipments API contains all the endpoints to create shipments and retrieve the data of your created shipments. You will also find the endpoints to receive notifications about the status updates of your shipments via a webhook.
When defining your integration, you can choose NOT to use our card distribution service.
In that case, the affinity groups will reflect the configuration you have chosen. Additionally, when creating a card or a batch of cards, we will return an identifier in the shipment_id
field, which we recommend you store in your integration as you will need it to make the pickup. The cards will be available for pickup at the embossing plant defined in the integration.
The endpoint /shipping/v1/
is used to create a new shipment of an innominated card. Keep in mind that to create a shipment, it is required that you have created a batch of innominated cards..
The region
field corresponds to:
The courier.tracking_url field in the response will be available once the shipment is confirmed by the corresponding logistics partner. Until then, it will have a null value.
documentNumber
and documentType
will not be required.additional_info
field is not available for use.region
field with the two-character UF code. Example: 'SP' for São Paulo
zip_code
field is optional, meaning you may choose not to send it.additional_info
field is not available for use.The additional_info
field will be available only for shipments using 99 Minutes logistics.
You can associate a shipment with the user to whom you will send the card by specifying the user_id in the body of the shipment.
The endpoint /shipping/v1/
allows you to search for a group of shipments based on the attributes you specify.
You will be able to filter and sort the shipments following this documentation.
The attributes for sorting are:
shipment_type
status
status_detail
created_at
The endpoint /shipping/v1/{shipment_id}
will be used to update the delivery address of a shipment.
To update the delivery address, the shipment must have a STATUS_DETAIL of one of the following values according to the carrier:
Courier | Allowed statuses |
---|---|
99 MINUTOS | PENDING, SHIPMENT_CONFIRMED, RECEIVED_BY_CARRIER, ROAD_TO_PICKUP, UNSUCCESSFUL_PICKUP, UNSUCCESSFUL_PICKUP,FAILED_DELIVERY_ATTEMPT |
ANDREANI | PENDING, END_OF_CUSTODY, DISTRIBUTION, WRONG_ADDRESS |
DOMINA | CALL_SCHEDULED, VISIT_SCHEDULED, CALL_FAILED_UNKNOWN, CLIENT_NOT_PRESENT, WRONG_ADDRESS, IN_TRANSIT, INCOMPLETE_ADDRESS, RECEIVED_BY_CARRIER, CALL_RESCHEDULED |
ESTAFETA | FAILED_DELIVERY_ATTEMPT |
FLASH | START_OF_CUSTODY |
You will not be able to create another address change request for a shipment while there is one pending.
To check the status of the request, you will need to interact with the endpoint Get shipping. In the request_status
field, you will see one of the following values:
If your request is rejected, you will continue to see the original shipping address.
The endpoint /shipping/v1/{shipment_id}
allows you to obtain information about a particular shipment.
Do you have questions about the status of the shipments? We explain what each one means in our documentation.
You must specify the shipment_id
to make the inquiry.
For shipments to a warehouse and also for those made in Mexico, we will not return an external tracking ID, but don't worry! We will keep you informed about the status of the shipment from the Dashboard and also via webhooks.
The endpoint /shipping/v1/{shipment_id}/history
allows you to obtain the status history of a particular shipment.
Do you have questions about the status of the shipments? We explain what each one means in our documentation.
You must specify the shipment_id
to make the inquiry.
The list of events is ordered in ascending order by update date, meaning the most recent status is at the end of the list.
You must include this endpoint in your service so that we can communicate shipping updates to you in real time.
If you have questions about how to set up a webhook, visit our documentation.
Find more information about the status of shipments in our documentation.
api-secret
you need to use in case multiple pairs of api-key
and api-secret
have been configured.The endpoint /shipping/v1/{shipment_id}/receiver
allows you to request the details of the person who received the shipment.
You will not be able to create a request while there is a pending one for that same shipment_id.
To check the status of the request, you will need to interact with the endpoint Get shipping. In the request_status
field, you will see one of the following values:
To see the card recipient's data, interact again with the endpoint Get shipping and read the received_by
field found within courier_additional_info
.