> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/integrations/marketing-automation/marketo/how-to-find-your-marketo-account-details.md).
# How to Find Your Marketo Account Details
#### Your Marketo API Endpoint
You can find this information in the **Admin > Integration > Web Services** page from the sidebar. It is called “**Endpoint”** under **REST API**.
#### Your Client ID and Client Secret
To create the Client ID and Secret, we need to create a new custom service. First, navigate to **Admin > Launchpoint**. Click “**New Service**”.
Give your service a descriptive name (like “HockeyStack integration”) and select “**Custom**” from the **Service** dropdown menu. Give it a description, then select a user from the **API Only User** dropdown menu and click on “**Create**”.
We have now created our custom service. You should be able to see it in your list of LaunchPoint services, along with a button next to it called “**View Details**”. Click on it to access your Client ID and Secret.
---
# 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://docs.hockeystack.com/integrations/marketing-automation/marketo/how-to-find-your-marketo-account-details.md?ask=&goal=
```
`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.