> For the complete documentation index, see [llms.txt](https://alenfive.gitbook.io/data-jellyfish/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alenfive.gitbook.io/data-jellyfish/ye-wu-dui-jie.md).

# 业务对接

### 增量同步例子，将A系统数据增量同步给B系统，A系统数据如下：

| id | name |
| -- | ---- |
| 1  | 王一   |
| 2  | 王二   |
| 3  | 王三   |

数据说明： id为自增长ID，用于实现增量同步

### 操作步骤，A,B系统分别提供数据拉取接口与数据接收接口，由JellyFish来完成从A系统拉取数据，然后推送到B系统

### 1.A系统数据拉取接口开发要求如下

1. 接口要求 POST BODY JSON请求
2. JellyFish每次调用会在BODY中传递参数{"offset":"1"} 参数值为上一次拉取到的数据的最后一条记录的偏移量字段，用于实现增量查询
3. 接口返回结果如下:

| 字段   | 描述                        |
| ---- | ------------------------- |
| code | "0" ：表示数据获取成功，其他值表示数据请求异常 |
| data | 接口返回的数据，值为list            |
|      |                           |

### 2. B系统数据接收接口开发要求如下

1. 接口要求 POST BODY JSON请求
2. BODY参数为A系统返回值data中list集合下的某个元素
3. 接口返回要求如下:

| 字段   | 描述                                          |
| ---- | ------------------------------------------- |
| code | "0" ：表示数据处理成功，其他值表示数据处理异常，会触发JellyFish的重新推送 |

### 3. JellyFish 同步策略配置如下

@管理员


---

# 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://alenfive.gitbook.io/data-jellyfish/ye-wu-dui-jie.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.