Postman & Testing

Setting up Postman

Create a dedicated folder named Legacy Despacho in your Postman collection. Use collection-level variables to avoid repeating credentials across requests:

Variable	Description	Example
legacyBasePath	Base URL for all Legacy Despacho services	https://$TENANT/apidev/legacy
legacyGuid	Your company API key	xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
legacyUsuario	Integration user email or username	integracion@empresa.com
legacyPassword	Integration user password	••••••••

Each request body then references these variables:

{
  "WSAutorizacion": {
    "Guid": "{{legacyGuid}}",
    "Usuario": "{{legacyUsuario}}",
    "Password": "{{legacyPassword}}"
  }
}

Recommended test cases per service

For each service, cover at least the following scenarios:

1. Valid request — correct credentials and valid parameters; expect Resultado: "OK".
2. Auth failure — wrong Guid or Password; expect an error Resultado.
3. Missing required field — omit a mandatory parameter; expect a descriptive error Mensaje.
4. No results — valid request with filters that return zero records; expect Resultado: "OK" with an empty collection.

Available services

The following services are live and can be tested immediately:

• WSGetServicios
• WSGetTareaMultimedia
• WSGeocoding
• WSReverseGeocoding
• WSGetArchivosMultimedia
• WSAltaServicio

These are the only services exposed on the Legacy Despacho surface. If your integration needs a service that is not on this list, contact the GeoTareas team before building against it.