FAQs

1. I’m sending requests to Engine’s API but not getting any response, what am I doing wrong

   • Please refer to (i) Required Fields in the Collecting User Information section and (ii) Post Request in the API Specifications section of the guide. It’s also possible that the Post Request Authorization and Body are correct but there are no available offers. If this issue persists, please reach out to the assigned contact at Engine.

2. What happens if I don't include fields marked as required?

   1. The Engine API will still respond with a success (200) response, assuming all else is correct with the request. The Engine API's 200 response means that endpoints/auth are correct, and no fields are malformed - this is by design (since the Engine API spans multiple product types, each with different requirements). The designation of a field as "required" means most of the Financial Institutions in that product vertical require that field to be present, and omitting that field means that all FIs who require that field will not allow us to post that lead to check eligibility.

3. I haven’t received approval from the Engine Compliance team or Financial Services partners yet, how can I see offers returned through the API?

   • Partners building a Native API integration can access mock offers before receiving approval. Reach out to your assigned contact at Engine to ask about enabling mock offers and please make sure to use the provided test token instead of the production token when testing.

4. I finished building the Native API integration, what’s next?

   • Partners building a Native API integration can access mock offers before receiving approval. Reach out to your assigned contact at Engine to ask about enabling mock offers and please make sure to use the provided test token instead of the production token when testing.

5. I am only seeing pending Responses but no actual offers, how do I obtain actual offers?

   • When utilizing the Asynchronous Flow endpoint, partners building a Native API integration need to make a secondary request to Engine’s Offers Endpoint to retrieve offers. Please refer to Asynchronous and Synchronous Flow Responses in the API Specifications section of the guide.