This call is for use by API client implementations that make use of the ticket cookie rather than the <ticket> parameter.
Invoking this call returns a null ticket cookie (with the name TICKET). In some cases, invoking API_SignOut results in applications at the local machine (the API client) being unable to access Quick Base applications until API_Authenticate is called for a new ticket cookie.
This call does not invalidate any tickets, nor log off the caller from any Quick Base applications, nor prevent further access of Quick Base applications. If the caller has saved a valid ticket, that caller can continue to use that ticket even after API_SignOut is called.
A string value that you want returned. It will not be handled by Quick Base but it will be returned in the response.
The originating request, for example, API_SignOut
Identifies the error code, if any. (See the Error Codes appendix for a list of possible error codes.)
0 indicates that no error was encountered.
Text that explains the error code.
"No error" indicates that no error was encountered.
Optional. Contains any udata value supplied in the request.
POST https://target_domain/db/main HTTP/1.0
where target_domain is the domain against which you are invoking this call, for example, quickbase.com. Read about this notation.
<?xml version="1.0" ?>
Did this help you? Give us a rating:
© 1999-2020 QuickBase, Inc. All rights reserved. Legal Notices.