... | ... | @@ -4,7 +4,7 @@ This documentation shows how integrating companies can access and consume this i |
|
|
|
|
|
## NAP - DATEXII
|
|
|
|
|
|
Through the operation **GET** to the *endpoint* **/ api / 1.0 / nap** it is possible to obtain all the events that are published in the *National Access Point* of Spain that DGT is responsible for. The returned data set follows the DATEXII standard.
|
|
|
Through the operation **GET** to the *endpoint* **/v1/nap** it is possible to obtain all the events that are published in the *National Access Point* of Spain that DGT is responsible for. The returned data set follows the DATEXII standard.
|
|
|
|
|
|
```xml
|
|
|
<?xml version="1.0" encoding="UTF-8"?>
|
... | ... | @@ -109,9 +109,7 @@ The format will be: |
|
|
|
|
|
In this *endpoint* you will obtain all the information published regarding use cases 1 (V16 signals), use case 2 (works and incidents) and use case 4 (publication by DGT Virtual Variable Message Panels) that are active at each moment.
|
|
|
|
|
|
The associated documentation can be found in the document [DESCRIPCIÓN API BANDEJA DE SALIDA](docs/20200529 API Bandeja Salida v.1.3.pdf). The relationship between the LINCE incidents and the iconography is described in [20191010_DGT30_0.xlsx](docs/20191010_DGT30_0.xlsx)
|
|
|
|
|
|
> https://bandejadesalida-dev.cmobility30.es:8443/api/1.0/getPmvvs
|
|
|
> https://pre.cmobility30.es/bandejadesalida/v1/getPmvvs
|
|
|
|
|
|
It is a POST type *endpoint* that requires to send a *body* in JSON format. This *body* will have at least two fields: **idcompany** (the cn of the certificate) and the **token**. In addition, others can be added to filter the content of the response.
|
|
|
|
... | ... | |