# FindLogisticSetting

endpoint for finding LogisticSetting model

Endpoint: GET /v1/configs/ecommerces/{ecommerce_id}/logistics/
Version: 1.0.0

## Path parameters:

  - `ecommerce_id` (string, required)
    The id of the e-commerce. Optional.

## Query parameters:

  - `slug` (string)
    The path of an URL identifying the e-commerce. Optional.

  - `group` (string)
    The group of the e-commerce. Several e-commerces can have the same group. Optional.

## Response 200 fields (application/json):

  - `delivery_note_type` (string)
    DeliveryNoteType

  - `ecommerce_id` (string)
    EcommerceID

  - `reminder_flow` (string)
    ReminderFlow

  - `return_logistics` (array)
    ReturnLogistics

  - `return_logistics.carrier` (string)
    carrier that is effectively handling the return
Example: CorreosExpress, Correos, etc

  - `return_logistics.provider` (string)
    provider is the platform that manages the creation of the return label
 Example: Sendcloud, OPS, etc
 Important: the value OPS means that the REVER ops team manages 
 the creation of the return label

  - `return_logistics.return_method` (string)
    type of return method: DROP_OFF, PICKUP...
    Enum: "NO_RETURN_METHOD", "HOME_PICK_UP", "DROP_OFF_POINT", "DELIVERY_PICKUP", "IN_STORE"

  - `return_logistics.when` (array)
    list of dynamic evaluations to determine if this logistics is available
 They are evaluated in order, and all of them must be true to evaluate 
 together as true (AND condition)
 IF not specified, is considered as true always
 protolint:disable:next REPEATED_FIELD_NAMES_PLURALIZED

  - `store_list_url` (string)
    StoreListUrl