Accessing JETNET Evolution from Apps

Some JETNET API endpoints return a pageurl in the response. This allows your application to link directly to full detail pages inside JETNET Evolution using a security token.

These URLs can be used to:

  • Display detail pages inside an iframe or modal
  • Provide quick access to JETNET Evolution records from your platform
  • Allow users to jump directly into Evolution from within a workflow

Token Requirement

For security purposes, these URLs require a valid securityToken to be passed as a query string parameter. If the token is missing or expired, the page will fail to load unless the user is already authenticated within the JETNET Evolution interface.

Example URLs

  • Company Page
    https://www.jetnetevolution.com/DisplayCompanyDetail.aspx?compid=[COMPID]&securityToken=[TOKEN]
  • Contact Page
    https://www.jetnetevolution.com/DisplayContactDetail.aspx?conid=[CONID]&securityToken=[TOKEN]
  • Aircraft Page
    https://www.jetnetevolution.com/DisplayAircraftDetail.aspx?acid=[ACID]&securityToken=[TOKEN]

Usage Tips

  • Several JETNET API requests return a “pageurl” in the results. This would typically apply to getCompany, getContact, and getAircraft requests/endpoints.
  • The URL provided represents a page within JETNET Evolution that can be used in a direct page call and/or IFRAME from other applications to see full pages relating to companies, contacts, and/or aircraft.
  • For security purposes, such page calls will require that the calling application pass the security token as a request variable. Otherwise, the page call will return a failure unless otherwise logged into to Evolution thru some other valid means.

Was this article helpful?

/