> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/employment-support-systems/employment-support-systems-and-sp-system-interface/introduction.md).

# Introduction

Interoperability between social protection and employment support systems ensures that individuals receive support in times of need, and also provide them with the support necessary to achieve long-term self-sufficiency.

This interface outlines standardized processes, data models, and APIs to link employment support systems with social protection systems. Its main goal is to ensure that workers receiving social protection support can be systematically guided and supported toward employment programs, while employment programs beneficiaries can access social protection when eligible. The standards do not dictate the operational details of either system; instead, they ensure that the required data is securely exchanged in the correct format and that both systems understand the shared information.

The Employment–Social Protection Interface provides a guideline for governments to move from siloed service delivery to an integrated, data-driven approach that supports:

* Social protection program beneficiaries to be referred to employment support programs
* Employment support beneficiaries to be referred to social protection services
* Systems operate efficiently and faster with less gaps, errors and duplication
* Services are delivered in a coordinated, person-centered way

This interface is a practical guide towards realizing the vision of integrated case management, where social protection and employment support programs work together as a seamless continuum of support.


---

# 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://standards.spdci.org/standards/dci-standards/employment-support-systems/employment-support-systems-and-sp-system-interface/introduction.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.
