返回提示词目录第 1420 页

撰写企业 API 合作接入申请

根据合作场景与对方要求,起草具体可信的 API 接入申请,说明权限范围、预期用量、安全措施及待核实信息。

完整提示词

<context>
Partner and restricted API requests are screened by someone at the other company who gets many vague asks and approves few. They approve requests that make a specific, credible case: a concrete integration their customers would use, realistic volume numbers, a clear statement of the data accessed and why, a security posture they can check (how tokens are stored, compliance reports the requester actually holds), and evidence the team can build and support it. Requests fail by being generic ("we'd love to partner"), overstating scale, asking for broad scopes "just in case", or ignoring the questions on the partner form.
</context>

<task>
Write the access request.

<request>
{{request}}
</request>
{{#their_requirements}}
<their_requirements>
{{their_requirements}}
</their_requirements>
{{/their_requirements}}

1. Open with who you are and the specific access requested in two sentences.
2. Describe the use case: what the integration does, for which users, and why it benefits the partner's customers or platform.
3. State the scopes or endpoints needed and why each is needed; drop anything not justified.
4. Give expected volume and growth honestly, and how you will respect rate limits.
5. Describe data handling and security: what data is stored, where, for how long, token storage, access controls, and any certifications only if the input states them.
6. Give the timeline and the technical contact.
7. Close with a concrete next step.
{{#their_requirements}}8. Make sure every listed requirement is answered, and map answers to their form fields.{{/their_requirements}}
</task>

<constraints>
- Do not invent customers, user numbers, certifications or security controls; use placeholders and list them.
- Request the narrowest access that serves the use case.
- Under about 300 words for an email; longer only if mapping to a form.
- Professional, specific, no hype.
</constraints>

<output_format>
## Request
Subject line and message, or form answers by field.

## Placeholders and checks
Facts to fill or verify before sending.
</output_format>

可替换内容

  • {{request}}
  • {{#their_requirements}}
  • {{their_requirements}}
  • {{/their_requirements}}

分类与标签

商业营销、API 接入、企业合作、商务邮件

前往 AI 图片创作