Getting Access

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

A LANDATA Account with web services access is required to use the Portal SOAP API. To request access, please contact: data.services@servictoria.com.au

You will receive:

• An Account ID for identifying your organisation
• Session credentials for authentication
• Access to the Test environment for development and testing

Authentication

The Portal SOAP API uses a session-based authentication model. Each SOAP request must include:

• accountId - Your assigned account identifier
• sessionId - A valid session ID obtained from the login process

Session Management

Sessions are established through the LANDATA Portal login process and have a limited lifetime. Your application should:

1. Obtain a session ID through the authentication process
2. Include the session ID in all subsequent API calls
3. Handle session expiry by re-authenticating when necessary

Request Structure

All Portal SOAP operations follow this general request structure:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
               xmlns:tns="http://Portal1.landata.vic.gov.au/Portal/WebServices">
  <soap:Body>
    <tns:OperationName>
      <tns:accountId>YOUR_ACCOUNT_ID</tns:accountId>
      <tns:sessionId>YOUR_SESSION_ID</tns:sessionId>
      <tns:customerReference>YOUR_REFERENCE</tns:customerReference>
      <!-- Operation-specific parameters -->
    </tns:OperationName>
  </soap:Body>
</soap:Envelope>

Customer Reference

The customerReference parameter is optional but recommended. It allows you to:

• Track requests in your own systems
• Associate API calls with your internal order references
• Facilitate reconciliation and troubleshooting

Environment URLs

Rate Limits

The Portal SOAP API has rate limiting in place to ensure fair usage. If you receive rate limit errors, implement exponential backoff in your retry logic.

More Information

For detailed WSDL specifications, see the WSDL Reference.