> For the complete documentation index, see [llms.txt](https://docs.snagajob.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snagajob.com/welcome-to-snagajobs-developer-documentation.md).

# Welcome to Snagajob's Developer Documentation

Here you will find all the documentation you need to start using Snagajob's APIs and become an integrated partner with Snagajob.

## Start by requesting an API secret here:

{% content-ref url="/pages/AunwEq1vWlPwMyNzdsfp" %}
[Obtaining API Access](/authentication/obtaining-api-access.md)
{% endcontent-ref %}

## The process of becoming an integrated partner of Snagajob

This document outlines the process of becoming an integrated vendor with Snagajob. Being integrated enables you and your customers to:

1. Create Snagajob accounts for your customers straight from your system
2. Automatically send your customer’s postings to Snagajob
3. Leverage Snagajob’s Easy Apply and have completed applications route directly to your system
4. Sponsor your customer’s postings on Snagajob to receive premium placement and visibility
5. Share data with Snagajob—transferring cost and candidate disposition data.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snagajob.com/welcome-to-snagajobs-developer-documentation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.