Flype Order API
  1. Locations
  • Flype Order API
    • Shipments
      • Rates
      • Create Bulk Orders
      • All Shipments
      • Shipments Count
      • Shipment Details
      • Shipment Last Status
      • Cancel Shipment
      • Get Shipping Label
    • Webhook
      • Webhook: Shipment status updates (Flype → Your Server)
    • Locations
      • Upsert Pickup Location
        POST
      • Get Saved Pickup Locations
        GET
      • Fetch Pickup Location Details
        GET
    • Schemas
      • ApiStatus
      • ErrorResponse
      • ShipmentsCountResponse
      • AllShipmentsRequest
      • ShipmentSummary
      • AllShipmentsResponse
      • BulkOrderRequest
      • BulkOrderResponse
      • SchedulePickupRequest
      • SchedulePickupResponse
      • City
      • GetCitiesResponse
      • ShipmentDetailsResponse
      • ShipmentLastStatusResponse
      • CancelShipmentResponse
      • LabelResponse
      • Country
      • CountriesResponse
      • ShipmentStatusWebhook
      • PlaceBulkItem
      • SuccessMessageResponse
      • PlaceBulkAddress
      • BooleanDataResponse
      • PlaceBulkPickupLocation
      • ShipmentAddress
      • PlaceBulkShipment
      • ShipmentRecipient
      • PlaceBulkAcceptedOrder
      • ShipmentRetailerAddress
      • PlaceBulkDeniedOrder
      • ShipmentRetailer
      • BulkOrderResponseData
      • ShipmentDriver
      • ShipmentStatusHistoryEntry
      • DeliverySettings
      • DropOffDetails
      • AllShipmentsItem
      • CitiesResponse
      • AirwayBillResponse
      • WebhookShipmentStatusUpdate
      • WebhookAckResponse
      • PlaceBulkDeliveryAddress
      • PlaceBulkRequest
  1. Locations

Upsert Pickup Location

POST
/locations

Create/Update Location Endpoint#

Create or update a pickup location (store/warehouse) in Flype.
Upsert behavior
If externalLocationId does not exist, Flype will create a new location.
If externalLocationId already exists, Flype will update the existing location (no duplicate created).

Why use Locations#

Reduces address errors and repeated data entry
Enables faster order creation by referencing a saved pickup location
Supports consistent pickup routing and reporting

External Location ID#

You may provide your own externalLocationId (recommended).
If not provided, Flype will generate a location ID and return it in the response. Save this ID and reuse it for future requests (e.g., /rates, PlaceBulk).

Location activation (Flype-controlled)#

New or updated locations may be created with a non-active status by default.
A location will not become active/usable until it is approved and marked active by Flype internally.

Update behavior#

If a location with the same externalLocationId already exists in Flype, the request will update the existing location (upsert behavior) instead of creating a duplicate.

Request

Authorization
Bearer Token
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
or
Body Params application/jsonRequired

Examples

Responses

🟢200
application/json
Bodyapplication/json

🟠400
Request Request Example
Shell
JavaScript
Java
Swift
cURL
curl --location '/locations' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
  "externalLocationId": "STORE_123",
  "name": "Store Name - Downtown",
  "address": {
    "street1": "233 West 52nd streeet",
    "street2": "Building 3",
    "city": "New York",
    "postalCode": "10101",
    "country": "United States"
  },
  "contact": {
    "name": "Pickup Desk",
    "phone": "+1501234567"
  },
  "notes": "Back door pickup"
}'
Response Response Example
200 - Created location success
{
  "status": "success",
  "data": {
    "externalLocationId": "STORE_123",
    "created": true
  }
}
Previous
Webhook: Shipment status updates (Flype → Your Server)
Next
Get Saved Pickup Locations
Built with