Skip to main content

​
Prerequisites

Before using the Alta Multes API webservice, you must complete the following requirements:

​
Administrative Requirements

1

Complete the adhesion process

Submit the adhesion form signed by the Mayor via EACAT.See the Adhesion Process page for detailed instructions.
2

Provide your public certificate

As part of the adhesion process, provide the public part of the certificate you will use to access the webservice.
The certificate must be communicated to ORGT before testing, as the public key needs to be installed on ORGT servers.
3

Register your devices

Communicate to ORGT all devices that will use the service so they can be assigned IMEIs and registered in the database.
You must notify ORGT each time you add a new device.

​
Technical Requirements

​
Authentication and Security

Access to the webservice is via HTTPS with certificate authentication for both client and server.
Key security aspects:
  • Protocol: HTTPS only
  • Client certificate: Required for all API calls
  • Server certificate: Verified by ORGT
  • Same certificate: Used for both pre-production and production environments

​
Data Format Requirements

​
Request and Response Format

Both POST requests and responses are in XML format.

​
Text Data Formatting

All text data must be in uppercase (MAYÚSCULES).

​
XML Field Ordering

For the AltaMulta endpoint, XML fields in the request body must be ordered alphabetically.
The ordering requirements:
  • First field must be: cdagen
  • Last field must be: viapen
  • All fields in between must be alphabetically sorted
See the example request for proper field ordering.

​
Testing Requirements

​
Pre-Production Testing

1

Test in pre-production first

Before using the production service, you must test in the pre-production environment.Pre-production URL:
https://pdaprv16.orgt.diba.cat/RestMultesPDA/svcMultesPDA.svc/rest/
2

Communicate certificate and IMEIs

Before testing in pre-production, communicate to ORGT:
  • The certificate you will use
  • The IMEIs that will be used for testing
3

Perform connectivity tests in production

After pre-production tests, you can test connectivity with the production environment.Production URL:
https://pda.orgt.diba.cat/RestMultesPDA/svcMultesPDA.svc/rest/
For production connectivity tests, use an agent code starting with “USU” (e.g., “USU1”). All fines with these agent codes are considered test data and will not enter the ORGT fine system.

​
API Endpoint Structure

You must append the endpoint name to the base URL.
Example for the ObtenirRang endpoint in pre-production: 
https://pdaprv16.orgt.diba.cat/RestMultesPDA/svcMultesPDA.svc/rest/ObtenirRang?pImei=123&pEstat1=1&pEstat2=1

​
Integration Resources

​
API Specification

The REST API specification is available via Swagger:
You can automatically generate your API client from the Swagger specification file.

​
WSDL Documentation

Although the WSDL is for the SOAP version, field names and explanations are the same for REST:
You can cancel the certificate request to access the WSDL documentation.

​
Validation Schema

The XML validation schema is available directly from the webservice: Pre-production schema: 
https://pdaprv16.orgt.diba.cat/RestMultesPDA/schema/svcMultesPDA.xsd
Production schema: 
https://pda.orgt.diba.cat/RestMultesPDA/schema/svcMultesPDA.xsd

​
Development Checklist

Before going live, ensure you have:
  • Completed the adhesion process
  • Provided your public certificate to ORGT
  • Received IMEI assignments for all devices
  • Implemented HTTPS with certificate authentication
  • Configured XML request/response handling
  • Implemented uppercase text formatting
  • Implemented alphabetical field ordering for AltaMulta requests
  • Successfully tested all endpoints in pre-production
  • Performed connectivity tests in production with “USU” agent codes
  • Validated XML responses against the schema

​
Getting Help

For questions about requirements or the adhesion process, contact ORGT through the official channels mentioned in your adhesion documentation.

Build docs developers (and LLMs) love

Get started for freeTalk to us