Reference Overview
4 min
this page is a short orientation use the linked reference pages when generating integration code or validating an sdk response main models model important fields device serial , marketname , platform , platformversion , state , issimulator , ispublic pool id , name allocation allocationid , deviceserial , position , expiresat session sessionid , allocationid , state , device and recording fields screenrecord filekey , downloadurl , duration application filekey , version , revision , downloadurl response fields can be null while device park is preparing or assigning a resource check identifiers before using them in the next sdk method examples allocation deviceserial can be null while waiting in the queue session enddate can be null while the session is active session videorecordurl can be null until recording processing finishes signed download urls can expire and should not be stored as permanent identifiers node js errors error meaning deviceparkconfigerror invalid sdk configuration or method argument deviceparkhttperror device park returned a non success response deviceparkserializationerror response json could not be parsed try { await client devices() list(); } catch (error) { if (error instanceof deviceparkhttperror) { console error(error status, error body); } else { throw error; } } java validates required configuration and arguments with illegalargumentexception never log credentials, tokens or authorization headers when reporting failures for exact fields, nullability and json shapes, see model contracts /reference/model contracts for catch patterns and timeout behavior, see error handling /reference/error handling handle failures configuration errors indicate missing or invalid client configuration http errors contain the response status and body returned by device park network failures and request timeouts can occur before a response exists; handle them separately from http errors preserve the original test failure when cleanup also fails cleanup failures attempt cleanup in this order stop active sessions release allocations that will not be reused close the sdk client log cleanup errors with their resource identifiers, but do not replace the original test error with a later cleanup error
