Stellar PHP SDK API Documentation

This defines the maximum time a transaction remains valid after submission. After this timeout, the transaction will no longer be accepted by the network.

Default: 300 seconds (5 minutes)

Unit: seconds

Note: This timeout represents the transaction validity window, not the actual execution time. Most contract invocations complete within a few seconds, but the longer window allows for network congestion and retry scenarios.

Reference: Soroban transaction lifecycle

Used for transaction validity windows to account for clock drift between client and server. Transactions are typically given a validity window that starts slightly in the past to account for minor time discrepancies.

Default: 10 seconds before current time

Unit: seconds

Example:

• Start time: current_time - 10 seconds
• End time: current_time + timeout

This prevents transactions from being rejected due to minor clock synchronization issues between client and network nodes.

Reference: Transaction time bounds best practices

Indicates that the server cannot process the request due to client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Common causes:

• Invalid transaction format
• Missing required parameters
• Malformed JSON

Indicates that the request could not be completed due to a conflict with the current state of the target resource.

Common causes:

• Transaction already submitted
• Resource version conflict
• State transition not allowed

Indicates that the server understood the request but refuses to authorize it. Unlike 401, authentication will not help.

Common causes:

• Insufficient permissions
• Rate limiting
• IP blacklisting

Indicates that the server encountered an unexpected condition that prevented it from fulfilling the request. This is a generic error message when no more specific message is suitable.

Common causes:

• Server misconfiguration
• Unhandled exception
• Database errors

Indicates that the server cannot find the requested resource.

Common causes:

• Account doesn't exist
• Transaction not found
• Invalid endpoint

Indicates that the request succeeded. The meaning of success depends on the HTTP method:

• GET: Resource fetched successfully
• POST: Resource created or action completed

This is the standard success response code.

Indicates that the server is not ready to handle the request. This is typically a temporary condition, such as:

• Server maintenance
• Server overload
• Network issues

The response may include a Retry-After header indicating when the client should retry.