Back to Engine.tech

FAQs

Requests:

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

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

    • 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. Is there any rate limit on Engine's APIs?

    • Engine's API has rate limits of 10,000 calls per second.

Responses (Offers, Marketing, and Display):

  1. I am only seeing pending responses but no actual offers. How do I obtain actual offers?

    • When integrating with Engine through Native APIs, partners need to make subsequent requests to Engine’s Offers Endpoint by polling GET originator/rateTables/:uuid to retrieve complete offers. Please refer to API Specifications - Response section for more details.

  2. Can we store the offers to remove the lag in fetching the offers so that later in the funnel the user does not have to wait to get offers every time?

    • There is no way for supply partners to remove the lag in fetching offers. We would need to pause the Financial Institutions partners that are causing the lag to reduce the lag. Please note that we do cache offers on our side (instead of pinging the lenders again), which helps reduce lag times.

  3. What is the expiration period for offers?

    • Offers expire 31 days after the offer wall is generated.

  4. Can we request fresh offers for a user? How soon can we refresh them?

    • The only way to request "fresh" offers for a user is to submit a new request to /leads/rateTables and obtain a new rate table for that user. Note that Engine caches the offers coming from Financial Institutions, so the rate table may contain some/all of the same offers as before, if within the caching period (but it is technically a new rate table).

  5. Can we retarget the users for the pre-qualified offers?

    • Yes, you can send out remarketing emails. Engine also has remarketing emails scheduled for those who receive an offer wall but do not engage/click. The emails will have a CTA driving to a generic partner page with their offer wall.

  6. What size are the logos of Engine's Financial Institution partners? What are the logo file types?

    • The logos are 300x180px in size. Most logos are .svg files.

Testing and Integration:

  1. I haven’t received approval from the Engine Compliance team or Financial Services partners yet. How can build and test offer display?

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

Attribution:

  1. Can I add lead identifiers to the API request?

    • Yes. You may append client tags when posting lead information to Engine.

  2. How can a funding event be attributed back to channel partners?

  3. Is end-to-end attribution on the lender side supported?

    • Attribution is only supported on Engine side. Our Financial Institution partners do not provide their full funnel performance.

PreviousAPI SpecificationsNextHome Equity Line of Credit (HELOC)

Last updated

Was this helpful?