Try the Tesla Jobs single posting API

- An unknown or no-longer-listed job id returns `404`. - Tesla sits behind bot protection, so this endpoint renders through a browser backend rather than a plain HTTP client. A posting that has not been read recently can take noticeably longer on its first request; once fetched it is served from cache on subsequent reads. - If that first fetch runs longer than the request budget, the endpoint returns `503` with a `Retry-After` header rather than holding the connection open until your client times out. The fetch continues in the background, so a retry after the advertised delay normally returns `200` straight away. Treat this `503` as "ask again shortly", not as a failure.