Skip to main content

Sessions

Zuora

  • 日本語のコンテンツは機械翻訳されており、補助的な参照を目的としています。機械翻訳の精度は保証できません。英語版が正となります。また、現時点では検索機能は日本語での検索をサポートしていません。翻訳に関するフィードバックについては、docs@zuora.comに送信してください。

  • US Data Center Customers: The SOAP API is no longer under active development. The legacy SOAP calls still function, but are now also available in REST.

    EU Data Center Customers: The SOAP API is not available. Please use the REST API.

    APAC Data Center Customers: The SOAP API is not available. Please use the REST API.

    Going forward, new features will only be available through the REST API. We strongly recommend that all integrations are done using the REST API.

    You can find the REST API documentation at https://www.zuora.com/developer/.

Sessions

  1. Last updated
    Jan 8, 2020
  2. Save as PDF

This topic provides information about Zuora sessions.

Number of Sessions to Create

Each session maps to a particular user, and all data created has the “Created By” information as that user. Zuora recommends using one session per user.

Session Timeout Value

The default timeout value is 15 minutes. However, this can be configured in the Zuora application, under Administrative Settings > Security Policies. There the session timeout can be changed from as low as 15 minutes to as long as 8 hours.

Validating Sessions

There is currently no way to verify a valid session. If a session is invalid, the system will return an INVALID_SESSION error, which means that you need to log in again. The recommended approach is to keep a timer and when it passes the configured threshold minus a margin (for example, if the threshold is 15 minutes, then the timer should expire in 10 minutes), to log in again and get a fresh session.

Handling INVALID_SESSION Errors

INVALID_SESSION errors can occur when the user's session has reached the configured threshold. The code should retry again with the credentials to obtain a valid session.