Qodex.ai

Remote Unlock

Number of APIs: 5

Performance Motor's Remote Unlock API allows users to lock and unlock PM-integrated cars remotely and control interior temperature via a webhook from an approved device or service.

remote unlock

Third-party services

Due to the rise of connected car services which require lock/unlock access to perform actions (i.e. mobile fueling trucks, car package drop off), the Remote Unlock service has been uncoupled from the Remote Start service and as of January 2020 and requires additional steps for verification and authentication. Balancing security with ease of interoperability for partners is top-of-mind for Performance Motors, and we have a team dedicated to vetting potential partners before they may access consumer vehicles. If you are representing a connected car service and would like to apply for access to the Remote Unlock service, please email remote.unlock@performancemotors.com.

How does this work with Remote Start and other PM APIs?

Long-time Performance Motors API consumers may remember that all PM services were previously contained in the same umbrella API service. As of the 2020 split to microservice architecture, that is no longer the case. As the Remote Unlock is under the highest tier of security access, any credentials acquired to use with the Remote Unlock service may be used with any other PM API, but not the other way around.

Logistically, when starting the car remotely, the car remains locked until a qualifying event triggers an unlock. Similarly, an Engine Off call has no effect on lock status.

Getting Started

We recommend starting in the APIs tab on the left vertical sidebar. Here, you can see the different APIs that are built by PM developers, as well as browse the API specifications. Once you are on the Define tab of an individual API, you will be able to see the associated resources (Documentation, Tests, Mock Servers, etc.), and navigate between the different API versions.

Over in the Collections view, you will notice that each request has an example response associated with it. By calling the mock server endpoint (just the base url replaced with one generated by Qodex's mock server generator), you will be able to access these sample responses without going through the registration/authentication process.

Associated Resources

  • There is an OpenAPI file that was used to generate this collection, which you can find in the APIs tab on the left vertical sidebar. As the API itself evolves, we will use the two-way git sync to update the spec from Bitbucket to Qodex, and thus translate those changes over to this documentation collection.

    • Be sure to check back to this collection before you start implementing, and click the Watch icon on the API to be alerted to any changes

  • Monitor: Under the Monitors tab on the same vertical toolbar, we have set up a monitor that runs the collection once a day and displays the results of the tests.

  • Mock Server: As this API is liable to expose sensitive information, we have set up a mock server to return example responses. You can still send the requests, just make sure the baseUrl variable is filled in with the monitor url to receive a response.

  1. Lock GET {{url}}/remote/lock

  2. Unlock GET {{url}}/remote/unlock

  3. Trunk Release GET {{url}}/remote/trunk

  4. Roof/Sunroof GET {{url}}/remote/roof/open

  5. Hood GET {{url}}/remote/hood