> For the complete documentation index, see [llms.txt](https://even-financial.gitbook.io/developer-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://even-financial.gitbook.io/developer-center/native-api-integrations/credit-cards-marketplace/collecting-user-information-for-credit-cards.md).

# Collecting User Information for Credit Cards

## Authentication and Account Setup

A representative from Engine by MoneyLion will set up an account and provide an authorization token to access the Engine API.

* To integrate with the Credit Cards API, an authorization token is required to authenticate requests to the Engine API. Ensure the token is included in the request headers; otherwise, the API will return an error.
* Test authorization tokens and production authorization tokens are separate. Requests made with a test token will not be reflected in performance reporting or payable events. Be sure to switch to the production token once testing is complete.

For more information, see the official API documentation: <https://engine.tech/docs/api-reference/#authentication>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://even-financial.gitbook.io/developer-center/native-api-integrations/credit-cards-marketplace/collecting-user-information-for-credit-cards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.