client

1.0.x
(0 reviews)
This API allows blocking the acceptance of packages at Punto Correos and Celeritas pick-up points if the package does not meet the pre-registration criteria, product type, and customer type.

CLIENT

- API Overview

- General aspects of Correos APIs

- API access reques

- Usage levels

API Overview :

This interface enables the functionality to block the admission of packages at Correos Points and Celeritas Points that do not meet the preregistration, product type, and customer type requirements.

API Details:

1. Implemented security policies:

- Client ID Enforcement

- Rate limiting SLA based

General API Usage

This API has a single endpoint (/shippingCode) which receives only one parameter.

Example of the parameter that receives the request:


curl "https://api1-intapp.correosdesa.es/logistics/client/request/client/PW427V0700046620108021L/8200010?app="app""

Ejemplo de respuesta que envía la aplicación

{
  "data": {
    "code": "PW427V0700046620108021L",
    "remitName": "EDGAR",
    "remitPhone": "642497605",
    "remitEmail": "ADAN.CANO.MORENO@NTTDATA.COM"
  }
}

API Access Request

From the Exchange itself, or from the API access portal being used, there will be an option to Request access. If you do not see this option, it means that the API does not allow access requests. Before a client application is allowed to consume an API, access to the API must be requested.

This API uses the security policy called Client ID Enforcement. First, the client application must request access to this API. The request will go through an approval flow, and once approved by the API owner, a client_id and client_secret pair will be provided via email. Once the API owners accept the request, the client will be granted the ability to make API requests provided that the HTTP request headers client_id and client_secret are correctly configured.

For more details about the security policy, please refer to: https://docs.mulesoft.com/api-manager/2.x/client-id-based-policies
resources/headers-05442936-b5eb-4f1d-9c72-aa4638b6b955-37a4222f-8d53-4909-a0c1-f4e8836487e3.png

Usage Levels

APIs may have different usage levels defined. When requesting access to an API, you will see indications of the usage level (SLA) offered by the API. Please note that some usage levels may have an associated cost.

To find out which usage levels apply to your API, you can review the API Overview section.

Reviews